About to blow away X, what do I need to backup?

[Net Llama!]

Sorry, i've got no clue on what is going on with glibc.  I havcen't yet
attempted the 4.2.1 upgrade (still have 4.2.0 on my boxes), and i've only
got 1 Caldera box remaining.  If i have time, i'll try it this weekend,
but its kinda doubtful.

On Fri, 13 Sep 2002, Tim Wunder wrote:

> Yeah, I was confused too when I re-read my post. All I can say is, it was late ;-)
>
> Originally, I attempted to compile 4.2.1, the source of which is 4.2.0 patched with the patch file provided by xfree86.org. When I ran into the compile problem with 'make install', I tried to install the 4.2.0 binaries, which seemed to work, except that my XF86Config-4 file, which worked fine in 4.1.0, didn't work with 4.2.0. I attempted to run cf86config to get a working X, but my attempts failed. It was late, and rather than continuing to screw with it 'til the wee hours, I punted, installing 4.1.0 from eW3.1.1 rpms. Which works. I now have essentially the same setup I had prior to attempting the 4.2.1 compile.
>
> See my other post today for the gory details of how compiling 4.2.1 failed.
>
> Thanks,
> Tim
>
>
> On 9/13/2002 9:49 AM, someone claiming to be Net Llama! wrote:
> > Tim, i'm very confused on what you're trying to install here, and how you
> > got it.  According to the xfree86.org site, 4.2.1 is a minor revision of
> > the full 4.2.0 release, which must be installed first.  Additionally,
> > there are no source tarballs for patch releases.
> >
> > So, what did you compile from source, and what are you trying to install?
> >
> > What I woudl recommend, is to build 4.2.0 from source, and install that.
> > Test it out first to ensure that it works ok.  If you can't get it to
> > work, then don't even bother with 4.2.1, cause it ain't gonna make things
> > any better.
> >
> > On Thu, 12 Sep 2002, Tim Wunder wrote:
> >
> >>Well, it's horked nontheless. And I apparently needed to backup other
> >>directories besides /etx/X11 and /usr/X11R6 (/usr/lib, maybe?)
> >>I re-installed X from the eW3.1.1 CD I have laying around, so I have 4.1.0
> >>back. For some screwy reason (that I don't feel like troubleshooting at this
> >>hour -- 11:30 PM EDT), when I tried to install 4.2.0 from binaries, my
> >>XF86Config-4 file wouldn't work.
> >>
> >>The error I get when attempting to install my compiled version of 4.2.1 is:
> >>make[3]: Entering directory
> >>`/data/Source_files/xfree86/4.2.0/xc/programs/xcmsdb'
> >>rm -f xcmsdb
> >>gcc -o xcmsdb -O2 -march=i686 -mcpu=i686 -ansi -pedantic -Wall
> >>-L../../exports/lib xcmsdb.o loadData.o -lX11
> >>-Wl,-rpath-link,../../exports/lib
> >>/lib/libdl.so.2: undefined reference to `atexit'
> >>make[3]: *** [xcmsdb] Error 1
> >>make[3]: Leaving directory
> >>`/data/Source_files/xfree86/4.2.0/xc/programs/xcmsdb'
> >>make[2]: *** [install] Error 2
> >>make[2]: Leaving directory `/data/Source_files/xfree86/4.2.0/xc/programs'
> >>make[1]: *** [install] Error 2
> >>make[1]: Leaving directory `/data/Source_files/xfree86/4.2.0/xc'
> >>make: *** [install] Error 2
> >>
> >>>From what I found browsing the net with lynx, this can only be corrected by a
> >>re-install of glibc from source. Not a task I'm willing to attempt tonight.
> >>I'll do some more investigating on this atexit error. I've gotten it when
> >>compiling parts of kde from cvs and know how to fix it there (add '-u atexit'
> >>to a line in the configure script), but am clueless how to fix/work around it
> >>with X.
> >>
> >>I'd like to hear from any COL users who know fixes to this atexit error.
> >>I'm currently using:
> >># rpm -qa|grep glibc
> >>glibc-devel-static-2.2.4-22
> >>glibc-2.2.4-22
> >>glibc-devel-2.2.4-22
> >>glibc-localedata-2.2.4-22