From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc 4.8: use /lib/ for AArch64
Date: Tue, 28 May 2013 15:56:14 +0200 [thread overview]
Message-ID: <51A4B77E.7070906@linaro.org> (raw)
In-Reply-To: <CCC27A1E-27F7-4D70-B7A5-30F2118D3D0C@gmail.com>
W dniu 28.05.2013 01:23, Khem Raj pisze:
> On May 27, 2013, at 7:40 AM, Marcin Juszkiewicz
> <marcin.juszkiewicz@linaro.org> wrote:
>> +++ b/meta/recipes-devtools/gcc/gcc-4.8/use-lib-for-aarch64.patch
>> @@ -0,0 +1,23 @@
>> +From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
>> +
>> +AArch64 is built with /lib/ as prefix but GCC 4.8 tries to use /lib64/
>> +path so build fails.
>> +
>> +It may affect builds when /lib64/ will be used but so far it is not
>> +default.
>> +
>
> Marcin,
>
> what is the multilib strategy for aarch64? i think using lib64 for
> 64bit and keep /lib for 32bit apps would be ideal so you can keep the
> existing apps running. In OE we have convoluted x86_64 where when not
> using mutlilib it uses /lib for 64bit apps and when doing multilib it
> does /lib64 for default 64bit apps and /lib for 32bit apps its quite
> confusing. For arm lets not follow those footsteps and use /lib64 for
> 64bit from the onset and then multilib can come later and will fit in
> nicely.
I will leave that decision to Riku as new meta-linaro maintainer.
My view is that so far AArch64 is still in kind of "testing phase" rather
then fully used system. Switch to /lib64/ would require far more patches
(gcc-4.7, eglibc etc) than switching to /lib/ which is used since we
started with this architecture.
next prev parent reply other threads:[~2013-05-28 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 14:40 [PATCH] gcc 4.8: use /lib/ for AArch64 Marcin Juszkiewicz
2013-05-27 23:23 ` Khem Raj
2013-05-28 8:07 ` Richard Purdie
2013-05-28 13:56 ` Marcin Juszkiewicz [this message]
2013-05-28 16:49 ` Khem Raj
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=51A4B77E.7070906@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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