From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] evtest: fix program_invocation_short_name undeclared
Date: Fri, 20 Mar 2015 14:09:47 +0100 [thread overview]
Message-ID: <20150320140947.38980613@free-electrons.com> (raw)
In-Reply-To: <1426803498-18890-1-git-send-email-ps.report@gmx.net>
Dear Peter Seiderer,
Adding Alexey from Synopsys in Cc.
On Thu, 19 Mar 2015 23:18:18 +0100, Peter Seiderer wrote:
> Add fallback in case program_invocation_short_name is undeclared,
> e.g. in case of some uclibc configurations.
>
> Fixes [1]:
> 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);
>
> [1] http://autobuild.buildroot.net/results/0fd/0fd36a0d79c4d82aedebb5aca8d3ce4214b1ed61
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Shouldn't we instead ask Synopsys to rebuild their toolchains with a
uClibc configuration that includes
UCLIBC_HAS_PROGRAM_INVOCATION_NAME=y, so that it matches the
default Buildroot uClibc and we don't have to add gazillions of
workarounds in multiple packages just to support the ARC external
toolchain?
Alexey ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-20 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 22:18 [Buildroot] [PATCH v1] evtest: fix program_invocation_short_name undeclared Peter Seiderer
2015-03-20 13:09 ` Thomas Petazzoni [this message]
2015-03-20 20:02 ` Alexey Brodkin
2015-03-20 20:22 ` Thomas Petazzoni
2015-03-23 22:32 ` Peter Korsgaard
2015-03-23 23:26 ` Thomas Petazzoni
2015-03-24 22:54 ` Peter Korsgaard
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=20150320140947.38980613@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