From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: lib64 not getting picked up
Date: Mon, 01 Aug 2011 17:58:47 +0100 [thread overview]
Message-ID: <1312217927.2344.513.camel@rex> (raw)
In-Reply-To: <4E36D43B.2060207@windriver.com>
On Mon, 2011-08-01 at 11:28 -0500, Mark Hatle wrote:
> On 8/1/11 11:15 AM, Kumar Gala wrote:
> > I'm trying to build a powerpc 64-bit system and for some reason everything is still in /lib instead of /lib64.
> >
> > I'd expect things in /lib64 based on how arch-powerpc64.inc has:
> >
> > BASE_LIB_tune-powerpc64 = "lib64"
> >
> > any ideas on what to look at for why this isn't happening?
> >
> > - k
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> in bitbake.conf try changing "baselib" to:
>
> baselib = "${@d.getVar('BASE_LIB_tune-${DEFAULTTUNE}', True) or 'lib'}"
FWIW, this is currently in multilib.conf so in non multilib configs, it
defaults to "lib" and in multilib, it defaults to the BASE_LIB settings.
If we want to use BASE_LIB in all cases its easy to change, I just felt
we could hold off on doing that for now, at least whilst we work through
some of the tune gremlins...
Cheers,
Richard
prev parent reply other threads:[~2011-08-01 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 16:15 lib64 not getting picked up Kumar Gala
2011-08-01 16:23 ` Phil Blundell
2011-08-01 16:28 ` Mark Hatle
2011-08-01 16:58 ` Richard Purdie [this message]
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=1312217927.2344.513.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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