Bug 2980

Please be more specific what is your cross setup, e.g. how you install the toolchain (tar ball, or adt_installer) what is the host and what is target, where is the toolchain installed at

Hello Jessica I downloaded and installed http://autobuilder.yoctoproject.org/pub/nightly/20120814-1/toolchain/x86_64/
and
http://autobuilder.yoctoproject.org/pub/nightly/20120819-3/toolchain/x86_64/

This bug is missing information. Which revision of the system was this built with? Which toolchain tarball was used (link to the tarball?)?

I gather you tested master as well and it has the same problem but please mention that here.

Hello Richard,
Sorry for the missing info:

the commits used are 91ece5d5668ee1adb5c5e3d757426a0d5187bd84 (for http://autobuilder.yoctoproject.org/pub/nightly/20120819-3/toolchain/x86_64/)
and 8b8748c8f963900b83dc0fdd7757556f917fe4fd for (http://autobuilder.yoctoproject.org/pub/nightly/20120814-1/toolchain/x86_64/)

Hello guys,
I identified the root cause of the problem:

The sh script to install the toolchain allows the user to select a location other than the default one (opt/poky/1.2+snapshot).
When any other location under the user's home directory is used this error occurs.
If the default location is used this is issue is not reproduce.

So this issue is not so critical.

Update for this bug:
the toolchain installed by ADT has the same issue.
http://autobuilder.yoctoproject.org/pub/nightly/20120814-1/adt_installer/

This bug might be related to some wrong permission settings after the relocation oad the sdk was implemented.
Another issue that might be linked to this is that trying to compile a simple C code fails due to some permission issue with the gcc 

-rwxr-xr-x 1 lserban root 2702282 Aug 10 07:09 /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc
lserban@laurentiu-02:/opt/poky/1.2+snapshot$ ${CC}
-bash: /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/armv5te-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc: Permission denied
lserban@laurentiu-02:/opt/poky/1.2+snapshot$ ls -al

(In reply to comment #5)
> Hello guys,
> I identified the root cause of the problem:
> 
> The sh script to install the toolchain allows the user to select a location
> other than the default one (opt/poky/1.2+snapshot).
> When any other location under the user's home directory is used this error
> occurs.
> If the default location is used this is issue is not reproduce.
> 
> So this issue is not so critical.

when use tar.bz2 tarball to test meta-toolchain before, the same also happened when use command "tar jxvf" to extract the tarball to the directory other than "/", so "/opt/poky/" is the directory meta-toolchain must exists in.

tar jxvf poky-eglibc-x86_64-arm-toolchain-gmae-1.2+snapshot-20120725.tar.bz2
source poky/1.2+snapshot/environment-setup-armv5te-poky-linux-gnueabi 
./configure ${CONFIGURE_FLAGS}

configure: WARNING: unrecognized options: --with-libtool-sysroot
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-poky-linux-gnueabi-strip... arm-poky-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc  -march=armv5te  -marm -mthumb-interwork  -mtune=arm926ej-s --sysroot=/opt/poky/1.2+snapshot/sysroots/armv5te-poky-linux-gnueabi
checking whether the C compiler works... no
configure: error: in `/home/liangli/new_package_need_to_compile/iptables_test/iptables-1.4.13':
configure: error: C compiler cannot create executables
See `config.log' for more details

This issue is related to the fact that the configure script that comes with the iptables archive is created for a different architecture than the one that we try to run it on (by sourcing the sdk), and so causing the compiler for arm, for example, to use a script designed for a different architecture.
The solution is to use the autotools (autogen.sh script in this case) to generate the correct configure script for the target architecture after sourcing the poky sdk.

Works fine on this build: http://autobuilder.yoctoproject.org/pub/nightly/20120916-2/

Setting it to verified.