From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] libgdiplus: new package
Date: Fri, 18 Dec 2015 20:04:46 +0100 [thread overview]
Message-ID: <20151218200446.384cdb38@free-electrons.com> (raw)
In-Reply-To: <CANu7NGt5xa9gWAxY4ha7VDbo0HxTNQ4VeMD7f4kD74tggmsdYw@mail.gmail.com>
Dear Sergio Prado,
On Fri, 18 Dec 2015 16:12:57 -0200, Sergio Prado wrote:
> Beaglebone with uclibc
> arm-buildroot-linux-uclibcgnueabihf-gcc: WARNING: unsafe header/library
> path used in cross-compilation: '/lib'
>
> Qemu x86 with glibc
> i686-buildroot-linux-gnu-gcc: WARNING: unsafe header/library path used in
> cross-compilation: '/lib'
>
> Why some toolchains generate an error and others a warning in this
> situation? Is there a configuration to enable this check when generating
> the toolchain?
It is not a matter of toolchain, it is a matter of whether you set the
option BR2_COMPILER_PARANOID_UNSAFE_PATH=y or not. By default it's
disabled, so those unsafe path messages are just warnings. In the
autobuilders, we turn this option on by default, so that just unsafe
path messages are treated as errors and abort the build.
This option simply sets an environment variable that makes the
toolchain wrapper error out when such unsafe paths are detected.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-18 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 0:15 [Buildroot] [PATCH v3] libgdiplus: new package Sergio Prado
2015-12-17 21:29 ` Thomas Petazzoni
2015-12-17 23:45 ` Sergio Prado
2015-12-18 10:41 ` Thomas Petazzoni
2015-12-18 10:56 ` Sergio Prado
2015-12-18 18:12 ` Sergio Prado
2015-12-18 19:04 ` Thomas Petazzoni [this message]
2015-12-18 19:13 ` Sergio Prado
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=20151218200446.384cdb38@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