[oe] ld segfault cant figure it out

[j]

On 04/13/2012 03:46 PM, j wrote:
> There seems to be a couple of packages when I build that cause ld 
> segfaults such as
> [ 6635.846581] ld[14419]: segfault at 8 ip 0077f1bf sp bfbf4a8c error 
> 4 in libc-2.13.so[73d000+15c000]
> [ 6656.831878] ld[20772]: segfault at 8 ip 00ba61bf sp bfaf1bfc error 
> 4 in libc-2.13.so[b64000+15c000]
>
> I can not seem to be able to track down the package/packages that are 
> causing this. I have tried with a clean build dir and only building 
> nano and I get it so it is something in the getting environment ready 
> steps. Is there a way I can easily track down the build/builds that 
> are causing this? Am I even on the right track in this thinking? 
> Nothing fails to build and other than task-native-sdk all result in 
> what seem to be working packages.
>
> Any info on what or how to figure it out would be greatly appreciated.
> building for bbxm on 11.04(uptodate), build environment setup with 
> Angstrom scripts and all is up to date.
>
> Thank you
Sorry forgot the info from qa.log

libgcc-4.5: non -staticdev package contains static .a library: 
libgcc-dev path 
'/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcc.a'
libgcc-4.5: non -staticdev package contains static .a library: 
libgcc-dev path 
'/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcov.a'
libgcc-4.5: non -staticdev package contains static .a library: 
libgcc-dev path 
'/work/armv7a-angstrom-linux-gnueabi/libgcc-4.5-r48+svnr184907/packages-split/libgcc-dev/usr/lib/arm-angstrom-linux-gnueabi/4.5.4/libgcc_eh.a'
bash-4.2: bash: Found a reference to /usr/ in 
/home/beagle/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/bash-4.2-r2/packages-split/bash/bin/bashbug
bash-4.2: Shell scripts in base_bindir and base_sbindir should not 
reference anything in exec_prefix

Any other places to check, as these I do not think relate to a segfault?