From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] autobuild-run: do not build evtest using extrenal arc-2014.12 toolchain
Date: Fri, 1 May 2015 23:10:02 +0200 [thread overview]
Message-ID: <20150501231002.1bd0f207@free-electrons.com> (raw)
In-Reply-To: <1427190703-2935-1-git-send-email-abrodkin@synopsys.com>
Dear Alexey Brodkin,
On Tue, 24 Mar 2015 12:51:43 +0300, Alexey Brodkin wrote:
> This external arc-2014.12 toolchain has uClibc with disabled
> UCLIBC_HAS_PROGRAM_INVOCATION_NAME.
>
> Because of this following build failure happens in autobuilder -
> http://autobuild.buildroot.net/results/0fd/0fd36a0d79c4d82aedebb5aca8d3ce4214b1ed61/
> --->8---
> evtest.c: In function 'version':
> evtest.c:730:20: error: 'program_invocation_short_name' undeclared (first use in this function)
> printf("%s %s\n", program_invocation_short_name, PACKAGE_VERSION);
> ^
> evtest.c:730:20: note: each undeclared identifier is reported only once for each function it appears in
> evtest.c: In function 'usage':
> evtest.c:742:38: error: 'program_invocation_short_name' undeclared (first use in this function)
> printf(" %s /dev/input/eventX\n", program_invocation_short_name);
> --->8---
I've marked this patch as Rejected, since I have committed another
patch to mark the Synopsys ARC external toolchain as "broken" because
the uClibc configuration is too far from the default Buildroot uClibc
configuration. We'll re-enable this toolchain once a new release is
made upstream, as we discussed.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-05-01 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:51 [Buildroot] [PATCH] autobuild-run: do not build evtest using extrenal arc-2014.12 toolchain Alexey Brodkin
2015-05-01 21:10 ` Thomas Petazzoni [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=20150501231002.1bd0f207@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox