From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SmRGk-0006Mb-Ik for openembedded-core@lists.openembedded.org; Wed, 04 Jul 2012 17:13:30 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q64F2RsQ024622 for ; Wed, 4 Jul 2012 16:02:27 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24103-05 for ; Wed, 4 Jul 2012 16:02:23 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q64F2HjG024612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 4 Jul 2012 16:02:18 +0100 Message-ID: <1341414137.3906.33.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Wed, 04 Jul 2012 16:02:17 +0100 In-Reply-To: References: <4FF453EC.8030007@linux.intel.com> <1341413143.3906.31.camel@ted> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: Re: gcc errors while building core-image-sato-sdk X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2012 15:13:30 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-07-04 at 17:50 +0300, Damian, Alexandru wrote: > The question wasn't why it fails, but why sometimes it goes through, > why sometimes fail, and why is it retriggered > without any changes to the config or files (run 5 times the > core-image-sato-sdk build in a row, and at least once it will fail). > > I don't trust systems that are not deterministic :). The check runs at the end of the do_configure task. The config.log is generated by do_compile. If do_configure is re-run, you'll hit the failure. > This being said: > > grep -C5 -e 'CROSS COMPILE Badness:' -e 'is unsafe for > cross-compilation' /home/ddalex/ssd/yocto/build/tmp/work/i586-poky-linux/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/build.i586-poky-linux.i586-poky-linux/gcc/config.log > | return ldopen (); > | ; > | return 0; > | } > configure:8836: i586-poky-linux-gcc -m32 -march=i586 > --sysroot=/home/ddalex/ssd/yocto/build/tmp/sysroots/qemux86 -o > conftest -pipe -g -feliminate-unused-debug-types -Wl,-O1 > -Wl,--hash-style=gnu -Wl,--as-needed conftest.c > -L/usr/lib/cmplrs/cc2.11 -lmld >&5 > /home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld: warning: library search path "/usr/lib/cmplrs/cc2.11" is unsafe for cross-compilation > /home/ddalex/ssd/yocto/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.7.2/ld: cannot find -lmld > collect2: error: ld returned 1 exit status > configure:8836: $? = 1 > configure: failed program was: > | /* confdefs.h */ So we need it to stop looking for libmld whatever that is. Hopefully there is a --disable-xxxx option we can pass in? Cheers, Richard