From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot-test 2/2] Enable paranoid path checking
Date: Fri, 26 Dec 2014 18:51:12 +0100 [thread overview]
Message-ID: <549DA010.6040205@openwide.fr> (raw)
In-Reply-To: <1418852858-818-2-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
Le 17/12/2014 22:47, Thomas Petazzoni a ?crit :
> 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?
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
>
Several packages have already been fixed since this feature has been
added. Enabling this check now will help to discover the remaining
packages left to fix.
Acked-by: Romain Naour <romain.naour@openwide.fr>
Best regards,
Romain
next prev parent reply other threads:[~2014-12-26 17:51 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
2014-12-26 17:51 ` Romain Naour [this message]
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=549DA010.6040205@openwide.fr \
--to=romain.naour@openwide.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