Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot-test 2/2] Enable paranoid path checking
Date: Thu, 18 Dec 2014 19:12:19 +0100	[thread overview]
Message-ID: <20141218181219.GA4589@free.fr> (raw)
In-Reply-To: <1418852858-818-2-git-send-email-thomas.petazzoni@free-electrons.com>

Thomas, All,

On 2014-12-17 22:47 +0100, Thomas Petazzoni spake thusly:
> Now that Buildroot has support for paranoid path checking (check for
> clearly invalid header and library directories used when
> cross-compiling), let's enable this in the autobuilders.
> 
> Without this, the paranoid path checking only emits warnings. With
> this patch enabled, whenever an invalid header or library path is
> used, the build will stop and fail, which will allow us to clearly
> notice such cases.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> Do we want to apply this right now? We already have a lot of failures
> caused by the static/shared change. Do we want to have more?

Well, either we set it right now, so we have time to investigate before
the 2015.02 release, or we post-pone that for after.

We're almost one mont in the release cycle, with a bit more than another
month before rc1, so it might be already too late for the switch, but it
is still doable.

So:

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2014-12-18 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 21:47 [Buildroot] [buildroot-test 1/2] Taking into account BR2_PREFER_STATIC_LIB rename Thomas Petazzoni
2014-12-17 21:47 ` [Buildroot] [buildroot-test 2/2] Enable paranoid path checking Thomas Petazzoni
2014-12-18  5:54   ` Bernd Kuhls
2014-12-18 18:12   ` Yann E. MORIN [this message]
2014-12-26 17:51   ` Romain Naour
2014-12-26 18:09     ` Thomas Petazzoni
2014-12-26 18:11       ` Romain Naour
2014-12-21 21:03 ` [Buildroot] [buildroot-test 1/2] Taking into account BR2_PREFER_STATIC_LIB rename Thomas Petazzoni
2014-12-21 21:13   ` Yann E. MORIN
2014-12-21 21:44     ` 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=20141218181219.GA4589@free.fr \
    --to=yann.morin.1998@free.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox