[Bug 4203] meta-toolchain: gcc-cross-sdk for arm/uclibc does not build

[bugzilla-daemon at amethyst.openembedded.net]

http://bugs.openembedded.net/show_bug.cgi?id=4203





--- Comment #2 from Jin <jin at mediatomb.cc>  2008-05-05 16:26:24 ---
Some more findings, I thought I'd retry it with oe.dev

gcc-cross-sdk did build in oe.dev, I only had to comment out this line in
do_populate_sdk() meta-toolchain.bb because the source directory was empty and
cp was failing:

#   cp -pPR ${SDK_OUTPUT}/temp-target/usr/share/*
${SDK_OUTPUT}/${prefix}/${TARGET_SYS}/share/

After that meta-toolchain did build and I went on testing it: scary stuff - the
libc.so.6 problem was present in the produced toolchain!

./arm-angstrom-linux-uclibcgnueabi-gcc -o /tmp/testout /tmp/test.c 
/opt/angstrom/arm/lib/gcc/arm-angstrom-linux-uclibcgnueabi/4.2.2/../../../../arm-angstrom-linux-uclibcgnueabi/bin/ld:
cannot find libc.so.6
collect2: ld returned 1 exit status

Why is it searching for libc.so.6??

test.c is just very simple testcode:
#include <stdio.h>
int main()
{
    printf("test\n");
    return 0;
}


I do not know how and why the toolchain that is used by OE internally (i.e. the
one in cross) works, but it obviously does - the same line above compiles
without any problems if I use the compiler from the cross/bin directory.

So what is flawed in the process and where?

-- 
Configure bugmail: http://bugs.openembedded.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.