Chmouel Boudjnah wrote:
> "Andrej Borsenkow" <[EMAIL PROTECTED]> writes:
>
> > > >
> > > > The result was a zero length, completely empty /etc/ld.so.conf.
> > > >
> > > > What should I put there to make sure applications always link to the
> > > > correct version of glibc? At present, I seem to only be able to get
> > > > linking working to one or the other, not both.
> > >
> > > no need to put anything /lib and /usr/lib is hardcoded and others
> > > programs put himself entry (XFree => /usr/X11R6/lib etc..)
> > >
> >
> > You missed the point. It was an *UPGRADE*; so glibc happily *erased* whatever
> > was put in by XFree et al.
>
> strange the ld.so.conf is :
>
> %verify(not md5 size mtime) %config(noreplace) %_sysconfdir/ld.so.conf
>
> so it should not be erased..
Unfortunately it did erase the old file, with the references to the lib5
compatibility directory. Also, remember from my original message that
I was NOT replacing every application, so I installed
compat-glibc-7.2-2.1.3.2mdk. This created a directory
/usr/i386-glibc-21-linux/lib, but did not put anything in ld.so.conf.
So none of the old applications linked against Mandrake 7.2 glibc would
start up (e.g. the old php-mysql). I could get them working if I ran
ldconfig /usr/i386-glibc-21-linux/lib, but then the applications linked
against the new glibc (such as the latest cooker version of Apache)
stopped working.
What I want to do is achieve a state in which my Mandrake 7.2 system can
run some cooker apps, without upgrading everything. That's what the
compatibility library should do, if it worked.
--
Dr. David R. Newman, Queen's University Belfast, School of
Management and Economics, Belfast BT7 1NN, Northern Ireland (UK)
mailto:[EMAIL PROTECTED] Tel. 028 90335011 FAX: 028 90249881
http://www.qub.ac.uk/mgt/staff/dave/
