> On Apr 26, 2016, at 1:41 AM, Richard Purdie
> <richard.pur...@linuxfoundation.org> wrote:
>
> On Mon, 2016-04-25 at 16:44 -0400, Tristan Van Berkom wrote:
>> Serializing this fixes build on aarch64
>> ---
>> meta/recipes-devtools/gcc/gcc-cross-initial.inc | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-devtools/gcc/gcc-cross-initial.inc
>> b/meta/recipes-devtools/gcc/gcc-cross-initial.inc
>> index c0fa139..98aae45 100644
>> --- a/meta/recipes-devtools/gcc/gcc-cross-initial.inc
>> +++ b/meta/recipes-devtools/gcc/gcc-cross-initial.inc
>> @@ -43,7 +43,8 @@ do_configure_prepend () {
>> }
>>
>> do_compile () {
>> - oe_runmake all-gcc configure-target-libgcc
>> + oe_runmake all-gcc
>> + oe_runmake configure-target-libgcc
>> }
>> do_install () {
>> ( cd ${B}/${TARGET_SYS}/libgcc; oe_runmake 'DESTDIR=${D}'
>> install-unwind_h )
>
> I'd note we have been doing aarch64 builds for a while and not run into
> this. What was the actual failure?
>
> Can we fix the underlying aarch64 problem, rather than breaking
> parallelism for everyone else this appears to be working for?
> I agree. and please add the relevant short error message that you were seeing > Cheers, > > Richard > > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
