All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ARC: update tools to arc-2015.06 release
Date: Fri, 17 Jul 2015 19:24:53 +0200	[thread overview]
Message-ID: <55A93A65.5070903@openwide.fr> (raw)
In-Reply-To: <1437147503.3374.9.camel@synopsys.com>

Alexey,

Le 17/07/2015 17:38, Alexey Brodkin a ?crit :
> Hi Romain,
> 
> On Fri, 2015-07-17 at 13:55 +0200, Romain Naour wrote:
>> Le 17/07/2015 13:45, Romain Naour a ?crit :
>>> Hi Alexey,
>>>
>>> Le 15/07/2015 14:51, Alexey Brodkin a ?crit :
>>>> I'm happy to update GNU tools for ARC cores to the most recent
>>>> arc-2015.06 release.
>>>>
>>>> This release brings following major improvements:
>>>>  * GCC: source update to v4.8.4
>>>>  * GCC: C ABI compatibility between MetaWare and GNU toolchains
>>>>  * uClibc: support for thread local storage and Native Pthread Library (NPTL)
>>>>  * GDB: updated to version 7.9.1
>>>>
>>>> Also a lot of fixes and improvements has been done, please refer to
>>>> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2015.06
>>>> for more details.
>>>>
>>>> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
>>>> Cc: Anton Kolesov <akolesov@synopsys.com>
>>>> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>>>> Cc: Peter Korsgaard <peter@korsgaard.com>
>>>> Cc: Romain Naour <romain.naour@openwide.fr>
>>>> ---
>>>>
>>>> I hope this time all required pieces are in place :)
>>>
>>> Your patch looks good, but I have a build failure with uclibc:
>>>
>>> make O=test/arc/ toolchain 2>&1 | tee build-arc-toolchain.log
>>>
>>>>>> uclibc arc-2015.06 Patching
>>> support/kconfig/merge_config.sh -m -O /home/naourr/git/buildroot/test/arc/build/uclibc-arc-2015.06 
>>> package/uclibc/uClibc-snapshot.config 
>>> Using package/uclibc/uClibc-snapshot.config as base
>>> #
>>> # merged configuration written to /home/naourr/git/buildroot/test/arc/build/uclibc-arc-2015.06/.config (needs make)
>>> #
>>>   MKDIR include/config
>>>   MKDIR include/generated
>>>   MKDIR extra/config/lxdialog
>>>   HOSTCC-o extra/config/conf.o
>>>   GEN extra/config/zconf.tab.c
>>>   GEN extra/config/zconf.lex.c
>>>   GEN extra/config/zconf.hash.c
>>> /bin/sh: test/arc//extra/config/zconf.hash.c: No such file or directory
>>> Makefile:70: recipe for target 'test/arc//extra/config/zconf.hash.c' failed
>>> make[3]: *** [test/arc//extra/config/zconf.hash.c] Error 1
>>> make[3]: *** Waiting for unfinished jobs....
>>> /bin/sh: test/arc//extra/config/zconf.tab.c: No such file or directory
>>> /bin/sh: test/arc//extra/config/zconf.lex.c: No such file or directory
>>> Makefile:70: recipe for target 'test/arc//extra/config/zconf.tab.c' failed
>>> make[3]: *** [test/arc//extra/config/zconf.tab.c] Error 1
>>> Makefile:70: recipe for target 'test/arc//extra/config/zconf.lex.c' failed
>>> make[3]: *** [test/arc//extra/config/zconf.lex.c] Error 1
>>> Assembler messages:
>>> Fatal error: can't create test/arc//extra/config/conf.o: No such file or directory
>>> Makefile:64: recipe for target 'test/arc//extra/config/conf.o' failed
>>> make[3]: *** [test/arc//extra/config/conf.o] Error 1
>>> Makefile.in:465: recipe for target 'test/arc//extra/config/conf' failed
>>> make[2]: *** [test/arc//extra/config/conf] Error 2
>>> package/uclibc/uclibc.mk:485: recipe for target '/home/naourr/git/buildroot/test/arc/build/uclibc-arc
>>> -2015.06/.config' failed
>>> make[1]: *** [/home/naourr/git/buildroot/test/arc/build/uclibc-arc-2015.06/.config] Error 2
>>> Makefile:36: recipe for target 'toolchain' failed
>>> make: *** [toolchain] Error 2
>>>
>>> It seems a issue related of out of tree build...
>>> The same issue happen with 2015.06-rc1/
>>>
>>> However, it build fine without 'O='.
>>>
>>> Humm, I tried to build different version of uClibc (-ng, -snapshot and -arc)
>>> and the out of tree build is broken.
>>>
>>> Yann, have you an idea, is it a kconfig-package issue ?
>>
>> I'm on master 0daffc0b65aa86d6d5bc6916736e0cffcdf540cc (setools: Add missing
>> bison dependency). So after "core/out-of-tree: fix Makefile wrapper".
> 
> It's pretty interesting.
> I'm on 5eb5f2710c2451d7e35dd600e6ced835efb9dda5 (funny enough it's your commit)
> "package/libmemcached: disable documentation" and for me ARC toolchain gets built
> with O=xxx (I always build out of tree).

This is weird, because uClibc doesn't build for me with O=, since
bee5745ccc20be6dbba243b1f8af0d5c522923e8 (Makefile: don't depend on the umask).

It seems that Arnout was not affected by this issue when reviewing/testing.
Also someone else reported this issue on IRC today.

My umask was 0002 and I had to set it to 0022 to workaround the issue.

Romain
> 
> So yes probably we're seeing some regression.
> 
> -Alexey
> 

  reply	other threads:[~2015-07-17 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 12:51 [Buildroot] [PATCH] ARC: update tools to arc-2015.06 release Alexey Brodkin
2015-07-17 11:45 ` Romain Naour
2015-07-17 11:55   ` Romain Naour
2015-07-17 15:38     ` Alexey Brodkin
2015-07-17 17:24       ` Romain Naour [this message]
2015-07-17 22:23   ` Yann E. MORIN
2015-07-17 22:54     ` Yann E. MORIN
2015-07-18  3:17       ` Guido Martínez
2015-07-25  9:24         ` Romain Naour
2015-07-18  9:14 ` Thomas Petazzoni

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=55A93A65.5070903@openwide.fr \
    --to=romain.naour@openwide.fr \
    --cc=buildroot@busybox.net \
    /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.