Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 21:22:13 +0100	[thread overview]
Message-ID: <20150320212213.21f2881e@free-electrons.com> (raw)
In-Reply-To: <1426881775.2897.10.camel@synopsys.com>

Dear Alexey Brodkin,

On Fri, 20 Mar 2015 20:02:58 +0000, Alexey Brodkin wrote:

> And for now I would propose to ignore mentioned build errors. Because
> indeed there's no point to throw in tons of temporary patches - if
> anybody really wants those "problematic" packages to be built there's
> always a possibility to build toolchain in Buildroot and it will use
> Buildroot's default uClibc config.
> 
> Will it work for you?

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.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-03-20 20:22 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 [this message]
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=20150320212213.21f2881e@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