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

[Tim Wunder]

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

Regards, 
Tim

On Thursday 12 September 2002 10:13 pm, Net Llama! wrote:
> I've done 4 builds of XFree86-4.x and the results have always been good.
>   Worst case was that i had to run xf86config to generate a better
> XF86Config file, but other than that it was quite painless.
>
> Tim Wunder wrote:
> > Well, that *is* an option. I've got a spare partition that I'm planning
> > (someday) to use to install a distro to replace the eW3.1 I'm currently
> > running. (Although, as much as I've updated this thing, I guess I really
> > can't call it eW3.1 anymore -- maybe I'll call it eW-TW3.1+. ) But, for
> > now, backup and go was the path of least resistance.
> >
> > Regards,
> > Tim
> >
> > (Woo-Hoo - X finally finished compiling -- time to really f'up my system
> > :-))
> >
> > On Thursday 12 September 2002 09:35 pm, m.w.chang wrote:
> >>that's why I experiement it on another harddisk first.
> >>I always wonder those distributors of linux would ever welcome customesr
> >>to escape her control ... some parents just don't want kids to grow up,
> >>like well, Mr. Love.
> >>
> >>Tim Wunder wrote:
> >>>That's fine, but I'm not the only user of this system, and if I hork X,
> >>> I need to recover quickly.
> >>>
> >>>>I didn't bother to backup. I chose to start from ground zero. :)

-- 
Caldera eWorkstation 3.1+, kernel 2.4.18-preempt, KDE 3.0.3, Xfree86 4.1.0
  8:00pm  up 5 days,  5:48,  2 users,  load average: 0.64, 0.36, 0.26
It's what you learn AFTER you know it all that counts