Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
Daniel Serodio [EMAIL PROTECTED] writes: On 2001.03.15 16:26:21 -0300 Chmouel Boudjnah wrote: David R Newman [EMAIL PROTECTED] writes: I tried upgrading glibc by installing glibc-2.2.2-4mdk andcompat-glibc-7.2-2.1.3.2mdk. Where can I find this RPM? Ive looked for it everywhere... in cooker : (chmou@no)[/RPMS]-% rpm -qpi compat-glibc-7.2-2.1.3.2mdk.i586.rpm Name: compat-glibc Relocations: (not relocateable) Version : 7.2 Vendor: MandrakeSoft Release : 2.1.3.2mdkBuild Date: Tue Jan 2 11:36:13 2001 Install date: (not installed) Build Host: ke.mandrakesoft.com Group : System/Libraries Source RPM: compat-glibc-7.2-2.1.3.2mdk.src.rpm Size: 7199968 License: LGPL Packager: Linux-Mandrake Team [EMAIL PROTECTED] Summary : GNU libc for Linux-Mandrake 7.2 backwards compatibility Description : This package contains the version 2.1.3 of the GNU C library for compiling binaries that will run on Linux-Mandrake 7.2 and other glibc 2.1.x Linux based systems. This package includes the runtime libraries. -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
On 2001.03.15 16:26:21 -0300 Chmouel Boudjnah wrote: David R Newman [EMAIL PROTECTED] writes: I tried upgrading glibc by installing glibc-2.2.2-4mdk andcompat-glibc-7.2-2.1.3.2mdk. Where can I find this RPM? Ive looked for it everywhere... -- []'s|.~. Daniel Serodio (lobo on irc)|/V\www.linux.org [EMAIL PROTECTED] | // \\ www.gnu.org | /( )\ www.gnome.org | ^`~'^
Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
"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.. -andrej -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
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.. -andrej -- MandrakeSoft Inc http://www.chmouel.org --Chmouel I've also have had the same problem when upgrading glibc. I found out after programs were unable to find libraries (in my mind, rebooting was not a option until i resolve the problem), I recreated the links manually. If I recall it did not make a backup of the existing ld.so.conf. It happened on both of my boxes (I was prepared for the second). This happened a few months ago when I had a 7.2 box and was upgrading glibc from the cooker ( i think glibc2.2.1-xxmdk) I also remember both times the glibc rpm complained about it needing ldconfig (did not mention newer version), even though it was allready installed (rpm -V ldconfig), on one box I installed the version of the 7.2 cdrom, on the other I downloaded the cooker ver. Didn't seem to make a difference though. Jose
Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
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/
Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
Is it a better option *NOT* to include /etc/ld.so.conf into glibc main package, and only create it inside %pre script *IF* it isn't a glibc upgrade? In that way upgrading glibc will never damage ld.so.conf! Abel Cheung On Fri, 16 Mar 2001, Jose wrote: I've also have had the same problem when upgrading glibc. I found out after programs were unable to find libraries (in my mind, rebooting was not a option until i resolve the problem), I recreated the links manually. If I recall it did not make a backup of the existing ld.so.conf. It happened on both of my boxes (I was prepared for the second). This happened a few months ago when I had a 7.2 box and was upgrading glibc from the cooker ( i think glibc2.2.1-xxmdk) I also remember both times the glibc rpm complained about it needing ldconfig (did not mention newer version), even though it was allready installed (rpm -V ldconfig), on one box I installed the version of the 7.2 cdrom, on the other I downloaded the cooker ver. Didn't seem to make a difference though. -- É£ã÷Îû, ʼØøħ... ʼØøÉù, É£ÞóÄÑ... É£ÄÑÎû, ʼÊÑħ... ʼÊÑÉù, ɣĴÉï... É£ÉïÉù, ʼèñħ... ʼèñÆÊ, É£Þóè÷...
[Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
I tried upgrading glibc by installing glibc-2.2.2-4mdk andcompat-glibc-7.2-2.1.3.2mdk. 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. -- 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/
Re: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
David R Newman [EMAIL PROTECTED] writes: I tried upgrading glibc by installing glibc-2.2.2-4mdk andcompat-glibc-7.2-2.1.3.2mdk. 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..) -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
RE: [Cooker] glibc-2.2.2-4mdk installs zero-length /etc/ld.so.conf
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. -andrej
