From: "Ross A. Towle" <rat@cchkms.engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] running ia32 binaries with same .so names as ia64
Date: Wed, 18 Oct 2000 01:49:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205587@msgid-missing> (raw)
Since Perl is not working for the SPEC harness, I have brought over
specperl that SPEC2000 distribution disk which is for RedHat6.0 and
later.
When I run it looks for an IA32 libgdbm.so.2 and reports "error in loading
shared libraries: libgdbm.so.2: ELF file class not 32-bit". So I copied it from
a IA32 box from /usr/lib and put it in /usr/i386-glibc21-linux/usr/lib. This
still does not fix the problem (same error message). But if I put it in
/usr/lib/temp and set LD_LIBRARY_PATH to /usr/lib/temp:$LD_LIBRARY_PATH
then everything runs fine.
Any ideas on how to do this without the LD_LIBRARY_PATH?
To generalize, if I want to bring over a IA32 binary linked against
some .so's with the same name(s) as on IA64, where do I place the IA32 .so's so
they are found without setting LD_LIBRARY_PATH?
-Ross
next reply other threads:[~2000-10-18 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-18 1:49 Ross A. Towle [this message]
2000-10-18 14:32 ` [Linux-ia64] running ia32 binaries with same .so names as ia64 Don Dugger
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=marc-linux-ia64-105590678205587@msgid-missing \
--to=rat@cchkms.engr.sgi.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.