[Buildroot] [v3, 12/12] Add option for paranoid unsafe path checking

Jörg Krause jkrause at posteo.de
Sat Dec 13 15:48:50 UTC 2014


On Sa, 2014-12-13 at 16:17 +0100, Romain Naour wrote:
> Hi Jörg,
> 
> Le 13/12/2014 15:11, Jörg Krause a écrit :
> > On Sa, 2014-12-13 at 01:19 +0100, Romain Naour wrote:
> >> Hello Jörg,
> >>
> >> Le 13/12/2014 01:04, Jörg Krause a écrit :
> >>> Hi Romain Naour,
> >>>
> >>> what should I do if a package build fails because of an unsafe path
> >>> error? Propose a patch for the package?
> >>>
> >>
> >> Yes, you needs patch the package's build system to remove the host path.
> > 
> > Many thanks! So hostpad and wpa_supplicant need patches.
> 
> You're welcome.

Many thanks for the invitation :)

> I didn't know that these packages were problems with the paranoid wrapper.

make[1]: Entering directory
'/home/joerg/Work/buildroot/output/build/wpa_supplicant-2.3/wpa_supplicant'
arm-linux-gcc: WARNING: unsafe header/library path used in
cross-compilation: '/usr/include/libnl3'

> 
> > 
> >>
> >> This error appear if one of the following paths is used during the
> >> cross-compilation:
> >> "/lib"
> >> "/usr/include"
> >> "/usr/lib"
> >> "/usr/local/include"
> >> "/usr/local/lib"
> > 
> > One more question: Why are these pathes unsafe for cross-compilation?
> 
> You have a good example here: 
> http://autobuild.buildroot.net/results/da0/da018caa1b79369bdff41d23b8696bc673625e1b/build-end.log
> 
> perl-gd try to link with the host (x86_64) libraries wile cross-compiling for mipsel target.
> It also include host headers path /usr/include
> 
> This is this kind of error we want to avoid before adding a new package or bumping version.
> 
I see. So instead of eg "/usr/include" "/include" should be used? And
instead of "/lib" "/"?




More information about the buildroot mailing list