2927 2012-08-09 14:50:23 +0000 the new Cross-Toolchain does not work with eclipse (Juno) 2012-08-28 13:38:25 +0000 1 1 6 Yocto Project Subprojects ADT adt 1.3 x86 Multiple VERIFIED FIXED http://autobuilder.yoctoproject.org/pub/nightly/20120808-1/toolchain/x86_64/poky-eglibc-x86_64-arm-toolchain-gmae-1.2+snapshot-20120808.sh (Scheduled) Medium+ normal 1.3 M4 1 alexandru.c.georgescu ioanax.grigoropol bogdan.a.marinescu jessica.zhang laurentiu.palcu poky.adt.watcher poky.watcher song.liu --- --- --- oldest_to_newest 23918 0 alexandru.c.georgescu 2012-08-09 14:50:23 +0000 The cross-toolchain already build by autobuilder does not work with Eclipse. IMAGE USED: http://autobuilder.yoctoproject.org/pub/nightly/20120808-1/toolchain/x86_64/poky-eglibc-x86_64-arm-toolchain-gmae-1.2+snapshot-20120808.sh STEPS TO REPRODUCE: 1. I have installed ADT with adt-insatller (build 0808-1). 2. I set up eclipse (Juno) with the new toolchain, sysroot, kernel image. I could build a new C ADT project. 3. I downloaded the 0808-1 toolchain file (specified above) and extracted it. 4. In eclipse I modified the sysroot with the new sysroot folder which was extracted at step 3. 5. Created a new project ( e.g. C Autotools project). 6. Reconfigure project, then try to build the project EXPECTED RESULT: The project can be build successful ACTUAL RESULT(from Eclipse): Description Resource Path Location Type make: *** No rule to make target `all'. C/C++ Problem in `/home/alex/workspactest7/dfsfsdf': dfsfsdf -1 Configure Problem C compiler cannot create executables dfsfsdf -1 Configure Problem OTHER: The toolchain works fine when installed with adt-installer. When using the Cross-Toolchain installation by hand, the errors appear. 23921 1 laurentiu.palcu 2012-08-09 15:32:08 +0000 It looks like it happens only on Alex's machine. The tollchain binaries fail with "Segmentation Fault". The same archive, works on other machines... Needs more investigations. 24082 2 laurentiu.palcu 2012-08-16 10:06:58 +0000 I found the root cause of this. It looks like toolchain binaries had the RPATHS hardcoded to the default path. If, for example, one installed the toolchain in the default location, /opt/poky/1.2+snapshot, and then tried an install in another location, the later install's toolchain binaries would search for libraries in the first location. If the libraries are found and loaded, a segmentation fault will occur. If the /opt/poky/1.2+snapshot directory does not exist at all, then everything is fine. The problem was in package.bbclass, the rpath_replace was called only for nativesdk packages and it should be called for cross-canadian packages too. I will send a fix shortly. 24535 3 ioanax.grigoropol 2012-08-28 12:13:42 +0000 LaurentiuP's latest patch set fixes this issue. 24539 4 alexandru.c.georgescu 2012-08-28 13:38:25 +0000 Setting to Verified - Fixed.