From: Dennis Wronka <linuxweb@gmx.net>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: "SE-Linux" <selinux@tycho.nsa.gov>
Subject: Re: best way to comile userspace to use lib64 for x86_64
Date: Tue, 4 Aug 2009 01:17:35 +0800 [thread overview]
Message-ID: <200908040117.41723.linuxweb@gmx.net> (raw)
In-Reply-To: <4A770542.3050103@gmail.com>
This can be quite hard at times. For most packages you can use --libdir with
configure, but some packages still want to put their stuff into /lib or /usr/lib
OpenSSL for example seems to require quite a few edits in the Makefiles.
Here's what I have to "rape" OpenSSL into installing into /usr/lib64
if [ "$(uname -a | grep x86_64)" != "" ]; then
for FILE in $(find . -name Makefile); do
sed -i 's@$(INSTALLTOP)/lib@&64@g' ${FILE}
sed -i 's@$${exec_prefix}/lib@&64@g' ${FILE}
done
fi
Btw, if you compile a pure 64-bit system I suggest simply linking /lib to
/lib64 and /usr/lib to /usr/lib64
Saves you lots of headaches with misplaced stuff...
> As an experimanet I'm building an x86_64 system, in doing so
> I'm noticing I need to have the libs point to /lib64 and /usr/lib64
> what is the easiest way to do this for the
> userspace from git. looking at the Makefiles seems a bit confusing,
> using LIBDIR=/lib64 does make /usr/lib64 but does not make /lib64.
>
> any ideas?
>
> Justin P. Mattock
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
> with the words "unsubscribe selinux" without quotes as the message.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-08-03 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 15:41 best way to comile userspace to use lib64 for x86_64 Justin P. Mattock
2009-08-03 16:09 ` Stephen Smalley
2009-08-03 16:40 ` Justin P. Mattock
2009-08-03 17:17 ` Dennis Wronka [this message]
2009-08-03 18:21 ` Justin P. Mattock
2009-08-03 18:29 ` Stephen Smalley
2009-08-03 22:11 ` Justin P. Mattock
2009-08-03 18:32 ` Dennis Wronka
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=200908040117.41723.linuxweb@gmx.net \
--to=linuxweb@gmx.net \
--cc=justinmattock@gmail.com \
--cc=selinux@tycho.nsa.gov \
/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.