Gentoo Archives: gentoo-user

From: Alan McKinnon <alan.mckinnon@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Installing an old glibc to run a proprietary commercial tool (would that even help?)
Date: Fri, 30 Oct 2009 21:59:34
Message-Id: 200910302358.25321.alan.mckinnon@gmail.com
In Reply to: Re: [gentoo-user] Installing an old glibc to run a proprietary commercial tool (would that even help?) by Kyle Bader
1 On Friday 30 October 2009 23:52:10 Kyle Bader wrote:
2 > Avoiding 1, 2, and 3 but thought I'd propose a 4 other than a virtual
3 > machine. Ask the vendor if they can provide a statically compiled
4 > version, that way you don't have to worry about libc. I dunno how
5 > flexible the vendor is but its worth asking :)
6
7
8 If it's a somewhat critical machine for business, just drop a new stand-alone
9 box running RHEL4. Critical machines usually generate|save more cash than the
10 cost of the box they run on
11
12
13
14
15
16
17
18
19 > On 10/30/09, Duncan Smith <duncanphilipnorman@×××××.com> wrote:
20 > > The company I work for is using gentoo on all its machines. We just
21 > > got a license to a commercial tool which does not support gentoo. The
22 > > closest thing it supports is RHEL v4.
23 > >
24 > > Running any command provided by the tool results in an explosive
25 > > memory leak (virtual memory hits 400G in 1 second, and continues to
26 > > climb).
27 > >
28 > > I suspect the problem is that RHEL v4 uses =sys-libs/glibc-2.3.4,
29 > > whereas we have =sys-libs/glibc-2.9_p20081201-r2 installed.
30 > >
31 > > I have three questions:
32 > > 1. Am I posting to the right list?
33 > > 2. Any idea what's going on? Could it be something other than glibc
34 > > causing the problem?
35 > > 3. If it is glibc, is there some way to install glibc slotted? Could
36 > > I install an old version of glibc to some other lib folder (like
37 > > /opt/lib64), and then use LD_LIBRARY_PATH somehow to get the tool to
38 > > look there first? How?
39 > >
40 > > Thanks for any help or ideas.
41 > >
42 > > Duncan
43 > >
44 > > P.S. In case it's useful, here is the output of ldd:
45 > > linux-vdso.so.1 => (0x00007fff9e3ff000)
46 > > libncurses.so.5 => /lib/libncurses.so.5 (0x00007f49c871b000)
47 > > libresolv.so.2 => /lib/libresolv.so.2 (0x00007f49c8503000)
48 > > libm.so.6 => /lib/libm.so.6 (0x00007f49c827e000)
49 > > libdl.so.2 => /lib/libdl.so.2 (0x00007f49c807a000)
50 > > libc.so.6 => /lib/libc.so.6 (0x00007f49c7d07000)
51 > > /lib64/ld-linux-x86-64.so.2 (0x00007f49c897a000)
52 >
53
54 --
55 alan dot mckinnon at gmail dot com