From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: what is up with lib64?
Date: Thu, 24 Jun 2004 02:44:00 +0100 [thread overview]
Message-ID: <40DA31E0.6010807@blueyonder.co.uk> (raw)
Cyrus Adkisson wrote:
> Can someone explain to me why x86_64 has lib64 directories and how
lib64 is supposed to work with the lib directories that are > already
there? I'm having a very difficult time getting anything to compile from
source.
>
> FC2, dual x86_64
lib is for 32-bit and lib64 is for 64-bit obviously. Build success here
is about 50%, a few build but won't run, segfaults etc.
The configure script in some apps needs the option --libdir=/usr/lib64
e.g. there is also a /lib64 and /usr/X11R6/lib64. Some apps will
configure and build without the need to adjust options. Some others will
not build as distributed, e.g kmymoney which keeps looking in /usr/lib
instead of /usr/lib64. There are yet others like slmodem that contain a
32-bit proprietary module for 2.4.x that will not be compatible with
2.6.x kernel sources.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
===== LINUX ONLY USED HERE =====
next reply other threads:[~2004-06-24 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 1:44 Sid Boyce [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 20:35 what is up with lib64? Cyrus Adkisson
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=40DA31E0.6010807@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox