[yocto] ADT Manual v1.1.1 Issues - 2 of 3 (Resolved)

Andy Gikling agikling at lasx.com
Tue Apr 10 06:50:24 PDT 2012


Lianhao,

Thank you for the insight.  I felt like this wasn't a bug!  I wasn't ever sure about where you are supposed to point for your sysroot.  Looking back through the ADT manual I see now what it's getting at.  Obviously it makes sense now.  Ahhh growing pains...

Thanks for your time - it works. 

~Andy Gikling

-----Original Message-----
From: Lu, Lianhao [mailto:lianhao.lu at intel.com] 
Sent: Tuesday, April 10, 2012 8:35 AM
To: Andy Gikling; yocto at yoctoproject.org
Subject: RE: ADT Manual v1.1.1 Issues - 2 of 3

Andy,

I checked the config.log. I think you might set the incorrect sysroot directory in Eclipse. The "/opt/poky/1.1.1/sysroots/" is incorrect, in your case it should be /opt/poky/1.1.1/sysroots/x86_64-poky-linux/. 

Please select your helloworld project, then select " Project -> Change Yocto Project Settings". Make sure you've set the correct sysroot directory. Then select "Project -> Reconfigure Project" to regenerate the configure sciprt.

I also recommend you pointing your sysroot location to where you've extracted core-image-sato-sdk. The sysroot under /opt/poky/1.1.1/sysroots/ x86_64-poky-linux/ contains only very limited header files and libraries.

-Lianhao

Andy Gikling wrote on 2012-04-10:
> Lianhao,
> 
> Attached is the config.log and the environment setup file.
> 
> I hope this gives us some insight.  Thank you for your time.
> 
> ~Andy Gikling
> 
> -----Original Message-----
> From: Lu, Lianhao [mailto:lianhao.lu at intel.com]
> Sent: Tuesday, April 10, 2012 12:08 AM
> To: Andy Gikling; yocto at yoctoproject.org
> Subject: RE: ADT Manual v1.1.1 Issues - 2 of 3
> 
> Andy,
> 
> Could you please attach both the config.log file and the environment file under the directory /opt/poky/1.1.1/ ?
> 
> Andy Gikling wrote on 2012-04-10:
>> All,
>> 
>> 
>> 
>> I've had very mixed results during the three or four times I've run 
>> through the ADT manual from scratch.  There seems to be a real 
>> problem I keep encountering that I'd like to describe to the 
>> community with the hope that someone understands why I keep getting 
>> stuck. I'm running a 32bit Ubuntu 11.10 VM and trying to build for a 
>> x86_64 sugarbay target machine.
>> 
>> 
>> 
>> The issue is that no matter which "route" I take to setup my 
>> toolchain (be it via the installer script or a premade toolchain I've 
>> downloaded) I always get "configure: error: C compiler cannot create executables"
>> when I try to use Project->Reconfigure Project after starting a new 
>> HelloWorld example in Eclipse.  The ADT manual explicitly steps the 
>> user through to this point but using the Reconfigure Project feature 
>> (that puts together your Makefile for you) never completes.  When 
>> looking closer at the config.log I always find something that looks 
>> like this:
>> 
>> 
>> 
>> configure:3285: $? = 0
>> 
>> configure:3274: x86_64-poky-linux-gcc -v >&5
>> 
>> Using built-in specs.
>> 
>> COLLECT_GCC=x86_64-poky-linux-gcc
>> 
>> COLLECT_LTO_WRAPPER=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/l
>> i bex ec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.6.3/lto-wra pper
>> 
>> Target: x86_64-poky-linux
>> 
>> Configured with:
>> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/buil
>> d /bu ild/tmp/work-shared/gcc-4.6.2+svnr181430-r17/gcc-4_6-branc
>> h/configure --build=x86_64-linux --host=i686-pokysdk-linux 
>> --target=x86_64-poky-linux 
>> --prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr
>> --exec_prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr
>> --bindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-p
>> o
>> ky-
>> linux
>> --sbindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-
>> p
>> oky
>> -linux
>> --libexecdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libexec/
>> x
>> 86_
>> 64-poky-linux
>> --datadir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share
>> --sysconfdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/etc
>> --sharedstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/com
>> --localstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/var
>> --libdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/lib/x86_64-p
>> o
>> ky-
>> linux
>> --includedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include
>> --oldincludedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/inclu
>> d e 
>> --infodir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/info
>> --mandir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/man
>> --disable-silent-rules
>> --with-libtool-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-sl
>> a ve/ 
>> nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativ
>> esdk --with-gnu-ld --enable-shared --enable-languages=c,c++ 
>> --enable-threads=posix --disable-multilib --enable-c99 
>> --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch
>> --program-prefix=x86_64-poky-linux- --enable-target-optspace 
>> --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp 
>> --disable-libmudflap --enable-cheaders=c_global 
>> --with-local-prefix=/opt/poky/1.1.1/sysroots/x86_64-poky-linux/usr
>> --with-gxx-include-dir=/usr/include/c++
>> --with-build-time-tools=/srv/home/pokybuild/yocto-autobuilder/yocto-s
>> l ave /nightly-x86-64/build/build/tmp/sysroots/x86_64-linux/usr/x86_
>> 64-poky-linux/bin
>> --with-sysroot=/opt/poky/1.1.1/sysroots/x86_64-poky-linux
>> --with-build-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slav
>> e
>> /ni
>> ghtly-x86-64/build/build/tmp/sysroots/qemux86-64
>> --disable-libunwind-exceptions --disable-libssp --disable-libgomp 
>> --disable-libmudflap
>> --with-mpfr=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly
>> -
>> x86 -64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk
>> --with-mpc=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-
>> x
>> 86- 64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk
>> --enable-nls --enable-__cxa_atexit
>> 
>> Thread model: posix
>> 
>> gcc version 4.6.3 20111117 (prerelease) (GCC)
>> 
>> configure:3285: $? = 0
>> 
>> configure:3274: x86_64-poky-linux-gcc -V >&5
>> 
>> x86_64-poky-linux-gcc: error: unrecognized option '-V'
>> 
>> x86_64-poky-linux-gcc: fatal error: no input files
>> 
>> compilation terminated.
>> 
>> configure:3285: $? = 1
>> 
>> configure:3274: x86_64-poky-linux-gcc -qversion >&5
>> 
>> x86_64-poky-linux-gcc: error: unrecognized option '-qversion'
>> 
>> x86_64-poky-linux-gcc: fatal error: no input files
>> 
>> compilation terminated.
>> 
>> 
>> 
>> I've tried to figure out what this error means but haven't had any 
>> luck.  People have made some suggestions that I've tried and they 
>> haven't worked either.  So, I've been told to file a bug about this 
>> but I wasn't sure which category it goes under and I've never filed a 
>> bug in the Yocto project before.  I'll try to get to it this week.
>> 
>> 
>> 
>> In the meantime, if anyone has tried to get through the ADT manual and is cross compiling I'd love to hear about how it went for you.
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> 
>> ~Andy Gikling
>> 
>> LasX Industries Inc.
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2411/4925 - Release Date: 
> 04/09/12

Best Regards,
Lianhao


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2411/4925 - Release Date: 04/09/12



More information about the yocto mailing list