From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installing an old glibc to run a proprietary commercial tool (would that even help?)
Date: Fri, 30 Oct 2009 23:58:25 +0200 [thread overview]
Message-ID: <200910302358.25321.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <854dca5c0910301452r78c1762dvbbd4748f7c602805@mail.gmail.com>
On Friday 30 October 2009 23:52:10 Kyle Bader wrote:
> Avoiding 1, 2, and 3 but thought I'd propose a 4 other than a virtual
> machine. Ask the vendor if they can provide a statically compiled
> version, that way you don't have to worry about libc. I dunno how
> flexible the vendor is but its worth asking :)
If it's a somewhat critical machine for business, just drop a new stand-alone
box running RHEL4. Critical machines usually generate|save more cash than the
cost of the box they run on
> On 10/30/09, Duncan Smith <duncanphilipnorman@gmail.com> wrote:
> > The company I work for is using gentoo on all its machines. We just
> > got a license to a commercial tool which does not support gentoo. The
> > closest thing it supports is RHEL v4.
> >
> > Running any command provided by the tool results in an explosive
> > memory leak (virtual memory hits 400G in 1 second, and continues to
> > climb).
> >
> > I suspect the problem is that RHEL v4 uses =sys-libs/glibc-2.3.4,
> > whereas we have =sys-libs/glibc-2.9_p20081201-r2 installed.
> >
> > I have three questions:
> > 1. Am I posting to the right list?
> > 2. Any idea what's going on? Could it be something other than glibc
> > causing the problem?
> > 3. If it is glibc, is there some way to install glibc slotted? Could
> > I install an old version of glibc to some other lib folder (like
> > /opt/lib64), and then use LD_LIBRARY_PATH somehow to get the tool to
> > look there first? How?
> >
> > Thanks for any help or ideas.
> >
> > Duncan
> >
> > P.S. In case it's useful, here is the output of ldd:
> > linux-vdso.so.1 => (0x00007fff9e3ff000)
> > libncurses.so.5 => /lib/libncurses.so.5 (0x00007f49c871b000)
> > libresolv.so.2 => /lib/libresolv.so.2 (0x00007f49c8503000)
> > libm.so.6 => /lib/libm.so.6 (0x00007f49c827e000)
> > libdl.so.2 => /lib/libdl.so.2 (0x00007f49c807a000)
> > libc.so.6 => /lib/libc.so.6 (0x00007f49c7d07000)
> > /lib64/ld-linux-x86-64.so.2 (0x00007f49c897a000)
>
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-10-30 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 14:01 [gentoo-user] Installing an old glibc to run a proprietary commercial tool (would that even help?) Duncan Smith
2009-10-30 15:24 ` Albert Hopkins
2009-10-30 15:26 ` Volker Armin Hemmann
2009-10-30 19:22 ` Duncan Smith
2009-10-30 19:37 ` Volker Armin Hemmann
2009-11-02 18:45 ` Duncan Smith
2009-10-30 21:52 ` Kyle Bader
2009-10-30 21:58 ` Alan McKinnon [this message]
2009-10-30 23:27 ` Albert Hopkins
2009-10-31 9:20 ` William Kenworthy
2009-11-02 18:52 ` Duncan Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910302358.25321.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox