From mboxrd@z Thu Jan 1 00:00:00 1970 From: Romain Naour Date: Sat, 13 Dec 2014 16:17:38 +0100 Subject: [Buildroot] [v3, 12/12] Add option for paranoid unsafe path checking In-Reply-To: <1418479863.2167.3.camel@posteo.de> References: <1418429047.1462.11.camel@posteo.de> <548B8601.8050109@openwide.fr> <1418479863.2167.3.camel@posteo.de> Message-ID: <548C5892.3070304@openwide.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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. I didn't know that these packages were problems with the paranoid wrapper. > >> >> 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. Best regards, -- Romain Naour OPEN WIDE Ing?nierie - Paris 23/25, rue Daviel| 75013 PARIS http://ingenierie.openwide.fr Le blog des technologies libres et embarqu?es : http://www.linuxembedded.fr