[OE-core] [PATCH] gcc 4.8: use /lib/ for AArch64

Khem Raj raj.khem at gmail.com
Tue May 28 16:49:40 UTC 2013


On May 28, 2013, at 6:56 AM, Marcin Juszkiewicz <marcin.juszkiewicz at linaro.org> wrote:

> W dniu 28.05.2013 01:23, Khem Raj pisze:
>> On May 27, 2013, at 7:40 AM, Marcin Juszkiewicz
>> <marcin.juszkiewicz at 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 at 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.


This is beginning of aarch64 and whatever defaults you set now will be harder to change as time passes
by. As I said earlier, if multilib and keeping precompiled 32bit binaries running is not priority then its fine. 




More information about the Openembedded-core mailing list