From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] evtest: fix program_invocation_short_name undeclared
Date: Tue, 24 Mar 2015 00:26:32 +0100 [thread overview]
Message-ID: <20150324002632.3aeef6e7@free-electrons.com> (raw)
In-Reply-To: <87bnjjgx9n.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Mon, 23 Mar 2015 23:32:52 +0100, Peter Korsgaard wrote:
> > Yes, it works. In the mean time, there is a way to avoid the build
> > errors: add an exception to the autobuilder script. See
> > http://git.buildroot.net/buildroot-test/tree/scripts/autobuild-run#n346
> > for a bunch of examples.
>
> Or simply make the packages depend on
> !BR2_TOOLCHAIN_EXTERNAL_SYNOPSYS_ARC_2014_12. Peter will you send
> patches to do that for evtest and libevdev?
This is indeed OK for packages such as evtest that don't have, or don't
have many, reverse dependencies. But this is hardly a sustainable
solution in general, especially for packages that have a high number of
reverse dependencies.
We simply can't handle all the little possible variations of uClibc
configurations that exist in every external toolchain, it's not
workable in a general fashion.
I know we're already doing it to some extent, but I'd like to avoid
doing it when possible, especially when we have a good cooperation with
the upstream developers (in this case, the Synopsys folks).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-23 23:26 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
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 [this message]
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=20150324002632.3aeef6e7@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