All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: best way to comile userspace to use lib64 for x86_64
Date: Mon, 03 Aug 2009 09:40:32 -0700	[thread overview]
Message-ID: <4A771300.8060900@gmail.com> (raw)
In-Reply-To: <1249315769.9193.2.camel@moss-pluto.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Mon, 2009-08-03 at 08:41 -0700, Justin P. Mattock wrote:
>    
>> 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?
>>      
>
> make LIBDIR=/usr/lib64 SHLIBDIR=/lib64 install
>    
ahhh..
Thank you so much for that.

Seems I needed to do this:

make DESTDIR=/home/justin/test LIBDIR=/home/justin/test/usr/lib64 \
SHLIBDIR=/home/justin/test/lib64 install

or else the libs would be put in /lib64 /usr/lib64 of the host system.

Anyways seems more of a pain to build such a system due to the
multilib thing.
(but what the heck might as well)

Thanks again.

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.

  reply	other threads:[~2009-08-03 16:40 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 [this message]
2009-08-03 17:17 ` Dennis Wronka
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=4A771300.8060900@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=sds@tycho.nsa.gov \
    --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.