On Thu, Aug 11, 2005 at 10:52:23PM -0300, bulia byak wrote:
On 8/11/05, Bryce Harrington <bryce@...1...> wrote:
This is one reason (although not a great reason) for having distro-specific (or glibc-specific) rpms.
Sigh.
I'm not saying we shouldn't make distro-specific rpms if it's really necessary. But it still does not look like something normal and acceptable, to me.
Well, you may not accept death or the IRS either. ;-) Fact is, this is exactly the issue that many, many ISVs face with Linux today.
A good third of the people at OSDL are working on projects related to this specific issue. The idea of a single binary package that installs cleanly on any Linux system is a holy grail of the industry.
I believe that it is possible to do a glibc detection as part of the rpm install; this may be a cleaner way of resolving the issue - just make the rpm fail to install if it's being installed against the wrong glibc.
Sounds like a good workaround. Anyone sufficiently RPM-savvy to set this up?
If it were me, I'd probably start by examining the RPM spec file for netscape, acrobat reader, or opera.
At least, can you tell me exactly which version(s) of glibc our static rpms require?
Probably 2.3.4.
bryce@...957... ~ $ ldd /usr/bin/inkscape | grep libc libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0xb74e8000) libc.so.6 => /lib/libc.so.6 (0xb6f4a000) bryce@...957... ~ $ ls -l /lib/libc.so.6 lrwxrwxrwx 1 root root 13 Jul 12 23:42 /lib/libc.so.6 -> libc-2.3.4.so
Bryce