[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 00026) using glibc-usagi simply and safely
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 00026) using glibc-usagi simply and safely
- From: "Alexandru Petrescu" <petrescu@xxxxxxx>
- Date: 10 Nov 2000 10:46:03 +0100
- Reply-to: "Alexandru Petrescu" <petrescu@xxxxxxx>
- Sender: petrescu@xxxxxxxxxxxxxxxxxxxxx
- User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
Installing a new libc has always been a sensitive issue and I wish I
had these instructions somewhere in README.USAGI before fiddling too
much with -L, -l, various env vars, and before my daemons were
`spawning too fast'.
Use your id, not root. First, patch the glibc and install it let's
say in --prefix=/glibc. Then bring a gcc-core and modify
gcc/config/i386/linux.h such that the hardwired string
/lib/ld-linux.so.2 becomes /glibc/lib/ld-linux.so.2. Next configure,
compile and install this gcc using the same --prefix=/glibc. Now you
can compile an usagi-improved ipv6 application with:
bash$ LD_RUN_PATH=/glibc/lib /glibc/bin/gcc improved.c
Thus, you don't need any special -l, -L, -nostdlib, LD_LIBRARY_PATH,
your old applications still run correctly. Moreover, you get rid of
the entire glibc-usagi with just rm -rf /glibc.
BTW, Hideaki, how do you use your glibc-usagi ?
PS: RedHat 6.2, gcc-core-2.95.2, i386.