Hi,
I intend to upgrade glibc. My preference is --prefix=/usr.
The FAQ warns that I should rename /usr/include as per below.
My question is after the upgrade what do with the old (renamed)
/usr/include headers?
--snip--
2.3. How should I avoid damaging my system when I install GNU libc?
{ZW} If you wish to be cautious, do not configure with --prefix=/usr. If
you don't specify a prefix, glibc will be installed in /usr/local, where
it will probably not break anything. (If you wish to be certain, set the
prefix to something like /usr/local/glibc2 which is not used for
anything.)
The dangers when installing glibc in /usr are twofold:
glibc will overwrite the headers in /usr/include. Other C libraries
install a different but overlapping set of headers there, so the effect
will probably be that you can't compile anything. You need to rename
/usr/include out of the way before running `make install'. (Do not throw
it away; you will then lose the ability to compile programs against your
old libc.)
None of your old libraries, static or shared, can be used with a
different C library major version. For shared libraries this is not a
problem, because the filenames are different and the dynamic linker will
enforce the restriction. But static libraries have no version
information. You have to evacuate all the static libraries in /usr/lib
to a safe location.
The situation is rather similar to the move from a.out to ELF which
long-time Linux users will remember.
--snip--
I have searched the archives & the net at large to no avail.
>Warm regards,
>Robert
>
>Robert Holmes- QA Chemist Phone: +61 2 9741 5234 Fax: +61 2 9748 4924
>Email: [EMAIL PROTECTED]
Both the individual sending this e-mail and The Lubrizol Corporation
intend that this electronic message be used exclusively by the individual
or entity to which it is intended to be addressed. This message may
contain information that is privileged, confidential and thereby exempt and
protected from unauthorized disclosure under applicable law. If the
reader of this message is not the intended recipient, or an employee or
agent responsible for delivering the message to the intended recipient,
be aware that any disclosure, dissemination, distribution or copying of
this communication, or the use of its contents, is not authorized and is
strictly prohibited. If you have received this communication and are not
the intended recipient, please notify the sender immediately and permanently
delete the original message from your e-mail system.
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
