Re: [oe] [oe-core] ld segfault cant figure it out
On 2012-04-19 18:39, j wrote: On 04/18/2012 11:24 PM, Khem Raj wrote: On Wed, Apr 18, 2012 at 8:32 PM, jvwyodap...@gmail.com wrote: on ubuntu edit /etc/security/limits.conf on build host and then add * soft core unlimited btw. reboot your machine after this change is made that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. I will do as suggested as well as do a full image build again and see if I can find out all that is not working. Thank you for the extra debugging info and suggestions. Are there any keywords to search through all the files for including the normal log files, it may help me track down things even further. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel did the reboot went through the build but yet did not produce any core files. But I noticed ulimit was still 0 so changed it to unlimited now and building again, hopefully that will get some core dumps. Will post back once I have more info and will separate anything by which machine as even the 2nd borrowed machine segfaults in the same way. Is your borrowed machine also running ArchLinux? If so, have you tried anything else - Ubuntu, Fedora, etc? As far as I can tell, you're the only one suffering these problems and also you seem to be the only one using ArchLinux. Note: I tried to duplicate your problems here, but I've never used ArchLinux and it's so primitive and hard to use (compared to what I use everyday) that I simply don't have the time to mess with it any more. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/20/2012 04:13 AM, Gary Thomas wrote: On 2012-04-19 18:39, j wrote: On 04/18/2012 11:24 PM, Khem Raj wrote: On Wed, Apr 18, 2012 at 8:32 PM, jvwyodap...@gmail.com wrote: on ubuntu edit /etc/security/limits.conf on build host and then add * soft core unlimited btw. reboot your machine after this change is made that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. I will do as suggested as well as do a full image build again and see if I can find out all that is not working. Thank you for the extra debugging info and suggestions. Are there any keywords to search through all the files for including the normal log files, it may help me track down things even further. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel did the reboot went through the build but yet did not produce any core files. But I noticed ulimit was still 0 so changed it to unlimited now and building again, hopefully that will get some core dumps. Will post back once I have more info and will separate anything by which machine as even the 2nd borrowed machine segfaults in the same way. Is your borrowed machine also running ArchLinux? If so, have you tried anything else - Ubuntu, Fedora, etc? As far as I can tell, you're the only one suffering these problems and also you seem to be the only one using ArchLinux. I have installed Ubuntu 10.04 and Fedora 16 on the borrowed machine as well. And still failing in the same manner. I am trying to do what Khem suggested and get core files but for some reason, even though it is saying I have it set to unlimited it is still not spitting anything out. I have abandoned Arch on the build machines for now as to keep that out of the variables. Note: I tried to duplicate your problems here, but I've never used ArchLinux and it's so primitive and hard to use (compared to what I use everyday) that I simply don't have the time to mess with it any more. It is not the only OS that does this for me. I am honestly surprised to hear Arch is hard, as that is how I see OE and trying to get a functioning build machine. :P I just got my 2nd borrowed machine today and starting to set it up now. Installing Ubuntu on it. If there is a single OS to install and try on all 3 I will happily do it again. But this is a non OS dependent thing is my guess since I am on 2 machines now that have done this. My QA.log's are still basically the same as well. all relating to LD type issues. I am still working through getting the image built on th1st borrowed machine it is slow and starting the Again OE classic(gumstix branch does not segfault on my machine that started all this it only started happening once I started trying to build a BBXM image on a new install on the same machine. If there is a OS and configuration to specifically try then outside of what is listed on the Angstrom pages and OE and your Distro pages please fill me in and will try. But as it stands now 2 totally different machines have gone through 3+ OS changes all have the same issue, all relatively the same issues and logs that were posted before. Should I attach more logs? ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/20/2012 04:13 AM, Gary Thomas wrote: On 2012-04-19 18:39, j wrote: On 04/18/2012 11:24 PM, Khem Raj wrote: On Wed, Apr 18, 2012 at 8:32 PM, jvwyodap...@gmail.com wrote: on ubuntu edit /etc/security/limits.conf on build host and then add * soft core unlimited btw. reboot your machine after this change is made that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. I will do as suggested as well as do a full image build again and see if I can find out all that is not working. Thank you for the extra debugging info and suggestions. Are there any keywords to search through all the files for including the normal log files, it may help me track down things even further. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel did the reboot went through the build but yet did not produce any core files. But I noticed ulimit was still 0 so changed it to unlimited now and building again, hopefully that will get some core dumps. Will post back once I have more info and will separate anything by which machine as even the 2nd borrowed machine segfaults in the same way. Is your borrowed machine also running ArchLinux? If so, have you tried anything else - Ubuntu, Fedora, etc? As far as I can tell, you're the only one suffering these problems and also you seem to be the only one using ArchLinux. Note: I tried to duplicate your problems here, but I've never used ArchLinux and it's so primitive and hard to use (compared to what I use everyday) that I simply don't have the time to mess with it any more. Also though not mentioned in my last email Gary THANK YOU!! 3rd machine has started build now. I installed 11.04 i386. This has intel graphics, where as the other 2 had nvidia. But this will be another slow build. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On Wed, Apr 18, 2012 at 8:32 PM, j vwyodap...@gmail.com wrote: on ubuntu edit /etc/security/limits.conf on build host and then add * soft core unlimited btw. reboot your machine after this change is made that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. I will do as suggested as well as do a full image build again and see if I can find out all that is not working. Thank you for the extra debugging info and suggestions. Are there any keywords to search through all the files for including the normal log files, it may help me track down things even further. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/18/2012 11:24 PM, Khem Raj wrote: On Wed, Apr 18, 2012 at 8:32 PM, jvwyodap...@gmail.com wrote: on ubuntu edit /etc/security/limits.conf on build host and then add * softcoreunlimited btw. reboot your machine after this change is made that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. I will do as suggested as well as do a full image build again and see if I can find out all that is not working. Thank you for the extra debugging info and suggestions. Are there any keywords to search through all the files for including the normal log files, it may help me track down things even further. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel did the reboot went through the build but yet did not produce any core files. But I noticed ulimit was still 0 so changed it to unlimited now and building again, hopefully that will get some core dumps. Will post back once I have more info and will separate anything by which machine as even the 2nd borrowed machine segfaults in the same way. Thanks again for the help ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On Tue, Apr 17, 2012 at 10:40 PM, j vwyodap...@gmail.com wrote: Sorry to sound so dumb but if there is no recipe failing and 2 separate systems are segfaulting in similar manners and both result with not fully functioning images/packages where else can I look for info? I posted all the logs to one of the builds, and the QA log seems to be the only thing really spitting out anything. I am open to trying and or sharing any and all relevant info to help sort it out or get me on track to sorting it out. what I am hearing is that your build succeeds despite these ld segfaults. Am I right ? but then when you run the resulting images then the images dont function correctly on your target and you also mentioned that its expat package when being built that causes the ld segfaults. Are you sure about that ? You could somehow forge ulimit to unlimited that will dump on ubuntu edit /etc/security/limits.conf on build host and then add * softcoreunlimited that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/18/2012 03:00 PM, Khem Raj wrote: On Tue, Apr 17, 2012 at 10:40 PM, jvwyodap...@gmail.com wrote: Sorry to sound so dumb but if there is no recipe failing and 2 separate systems are segfaulting in similar manners and both result with not fully functioning images/packages where else can I look for info? I posted all the logs to one of the builds, and the QA log seems to be the only thing really spitting out anything. I am open to trying and or sharing any and all relevant info to help sort it out or get me on track to sorting it out. what I am hearing is that your build succeeds despite these ld segfaults. Am I right ? but then when you run the resulting images then the images dont function correctly on your target First off thank you all for your time and information, and putting up with me learning and trying to get things working!! Yes you are correct. Nothing in the images or packages fail, but the build machine itself segfaults. Then if I put the image on my BB-XM sdcard they boot and run but things are not right, such as directories that should not be there are, some do not build a fully functioning package, such as task-native-sdk. and you also mentioned that its expat package when being built that causes the ld segfaults. Are you sure about that ? You could somehow forge ulimit to unlimited that will dump No I am not sure about it. As I am just trying to watch it build and look for the build machine to segfault and see what packages it is working on. Though after further messing with expat I think you are correct in doubting that is the one causing it. I just did a clean build of perl with no rm_work enabled, and I am trying to dig through the logs and info. From your earlier advice/mentioning of libtool-cross I do notice some things while it is building according to the info. I will post some of what stood out to me, which may in turn mean nothing. If I can post anymore of the logs or anything please let me know. I did notice today setting things to build one at a time, that it does appear that its working on libtool-cross, but again I could be wrong. on ubuntu edit /etc/security/limits.conf on build host and then add * softcoreunlimited that should generate core files. After this search for core* files in build tree and see if there are any then debug them with gdb to diagnose it further Now I am not sure if those segfaults directly relate to malfunction of image if thats the case but its likely. You should also try to explore the reasons why the image fails to behave as expected. I will do as suggested as well as do a full image build again and see if I can find out all that is not working. Thank you for the extra debugging info and suggestions. Are there any keywords to search through all the files for including the normal log files, it may help me track down things even further. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel I really am not trying to be a pain in the a** and would like to get things sorted out and understood on my side. Honestly if the resulting images worked and did not get any extra folders in their paths I would not care about the resulting segfaults on the build machine. Another side note, I am borrowing another build machine for a few days to see, this is a non nvidia machine just in case that is the bad variable in both machines. libtool-cross info:: log.do_configure /configure: WARNING: unrecognized options: --disable-silent-rules, --with-sysroot/ log.do_compile: help2man is installed on the system, whereis help2man help2man: /usr/bin/help2man /usr/lib/help2man /usr/share/man/man1/help2man.1.gz /WARNING: `help2man' is missing on your system. You should only need it if you modified a dependency of a manual page. You may need the `Help2man' package in order for those modifications to take effect. You can get `Help2man' from any GNU archive site. PATH=.:$PATH; export PATH; /bin/sh /home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.4.2-r2.1/libtool-2.4.2/libltdl/config/missing --run help2man --output=doc/libtoolize.1 libtoolize WARNING: `help2man' is missing on your system. You should only need it if you modified a dependency of a manual page. You may need the `Help2man' package in order for those modifications to take effect. You can get `Help2man' from any GNU archive site./ log.do_package /DEBUG: Preparing tree /home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.4.2-r2.1/shlibs for packaging at /home/gusterson/OpenEmbed/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.4.2-r2.1/sstate-build-package/shlibs sed: no
Re: [oe] [oe-core] ld segfault cant figure it out
On 2012-04-17 09:41, J. L. wrote: Well I borrowed a tower from a friend setup everything on a fresh install for both OS and build environment. Well I am still getting the same issue so it must not be an actual hardware issue. The first was trying to be built on my laptop, now trying this tower I get the same results just starting from scratch and building perl. What are your exact details - OS Angstrom (versions, etc). I'll try and run the same process here if you'll send enough details to reproduce exactly what you've done (which should be straight forward to provide since you just [re]did it yourself). I tried building just gcc and bash and well after cleaning them and I am not seeing anything that sticks out to me. Other than the errors and what not. Can anyone help me figure this out. Since it is now for sure not a hardware issue, die to same results on 2 machines. I have attached the cooker logs and qalogs incase they could be of any use in helping figure out the issue. Thank your for your time and help QALOG 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' 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.a' bash-4.2: bash: Found a reference to /usr/ in /home/gooms/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 SEGFAULT [10582.729446] ld[24926]: segfault at 8 ip b75ba427 sp bff61970 error 4 in libc-2.15.so[b7576000+19b000] [10596.912141] ld[30317]: segfault at 8 ip b758e427 sp bfbac350 error 4 in libc-2.15.so[b754a000+19b000] On Mon, Apr 16, 2012 at 6:43 PM, jvwyodap...@gmail.com wrote: On 04/16/2012 03:34 PM, j wrote: On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+**197000] [ 6444.526227] ld[31806]:
Re: [oe] [oe-core] ld segfault cant figure it out
OS - Arch Linux i686 fully up to date, Kernel's tried 3.3.1 3.0.27 Build machines: 1. Toshiba qosmio x505-887 laptop 2. Dell XPS tower I can give exact hardware specs if needed. Setup how Angstrom site says to for their build environment setup secripts. Packages installed are all on OE and your distro plus I was also missing cpio. OE Build Configuration: BB_VERSION= 1.15.1 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= v2012.04-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon Once the environment is setup, I source my environment file then I just run bitbake perl or bitbake virtual/kernel both give the segfaults. It appears the segfaults happen during teh build tools setup. Right around when bitbake pulls gcc into the line up to start building. That is all I have done each time. If there is more info you need please let me know and I will gladly reply with it. I thank you emensly for your continued help with this Gary!! JL On Tue, Apr 17, 2012 at 8:54 AM, Gary Thomas g...@mlbassoc.com wrote: On 2012-04-17 09:41, J. L. wrote: Well I borrowed a tower from a friend setup everything on a fresh install for both OS and build environment. Well I am still getting the same issue so it must not be an actual hardware issue. The first was trying to be built on my laptop, now trying this tower I get the same results just starting from scratch and building perl. What are your exact details - OS Angstrom (versions, etc). I'll try and run the same process here if you'll send enough details to reproduce exactly what you've done (which should be straight forward to provide since you just [re]did it yourself). I tried building just gcc and bash and well after cleaning them and I am not seeing anything that sticks out to me. Other than the errors and what not. Can anyone help me figure this out. Since it is now for sure not a hardware issue, die to same results on 2 machines. I have attached the cooker logs and qalogs incase they could be of any use in helping figure out the issue. Thank your for your time and help QALOG 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' 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.a' bash-4.2: bash: Found a reference to /usr/ in /home/gooms/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 SEGFAULT [10582.729446] ld[24926]: segfault at 8 ip b75ba427 sp bff61970 error 4 in libc-2.15.so[b7576000+19b000] [10596.912141] ld[30317]: segfault at 8 ip b758e427 sp bfbac350 error 4 in libc-2.15.so[b754a000+19b000] On Mon, Apr 16, 2012 at 6:43 PM, jvwyodap...@gmail.com wrote: On 04/16/2012 03:34 PM, j wrote: On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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
Re: [oe] [oe-core] ld segfault cant figure it out
I forgot to note angstrom version being used DISTRO = angstrom-2010.x On Tue, Apr 17, 2012 at 8:54 AM, Gary Thomas g...@mlbassoc.com wrote: On 2012-04-17 09:41, J. L. wrote: Well I borrowed a tower from a friend setup everything on a fresh install for both OS and build environment. Well I am still getting the same issue so it must not be an actual hardware issue. The first was trying to be built on my laptop, now trying this tower I get the same results just starting from scratch and building perl. What are your exact details - OS Angstrom (versions, etc). I'll try and run the same process here if you'll send enough details to reproduce exactly what you've done (which should be straight forward to provide since you just [re]did it yourself). I tried building just gcc and bash and well after cleaning them and I am not seeing anything that sticks out to me. Other than the errors and what not. Can anyone help me figure this out. Since it is now for sure not a hardware issue, die to same results on 2 machines. I have attached the cooker logs and qalogs incase they could be of any use in helping figure out the issue. Thank your for your time and help QALOG 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' 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.a' bash-4.2: bash: Found a reference to /usr/ in /home/gooms/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 SEGFAULT [10582.729446] ld[24926]: segfault at 8 ip b75ba427 sp bff61970 error 4 in libc-2.15.so[b7576000+19b000] [10596.912141] ld[30317]: segfault at 8 ip b758e427 sp bfbac350 error 4 in libc-2.15.so[b754a000+19b000] On Mon, Apr 16, 2012 at 6:43 PM, jvwyodap...@gmail.com wrote: On 04/16/2012 03:34 PM, j wrote: On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/17/2012 09:13 AM, J. L. wrote: snip http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel I went for a build on the borrowed machine again but this time I did not go into X just stayed in RL3. Then ran bitbake perl, on a clean build dir. It is just about to finish building a few steps away but where I normally get the segfaults, it has not spit those out. There are no QA logs being generated either. So looks like it had/has something to do with running X, both systems are running nvidia graphics cards. The laptop has a new mobile one, borrowed an old one that is nouveau compatible. So both open and closed nvidia drivers were tried. But something when in the graphical environment is giving the segfault issues I have been seeing. I have not yet verified if killing X on the laptop builds and eliminates the issues as well. Will post back once I have built the kernel on both machines with no X running. Thank you ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/17/2012 12:34 PM, Mark Hatle wrote: On 4/17/12 2:09 PM, j wrote: On 04/17/2012 09:13 AM, J. L. wrote: snip http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel I went for a build on the borrowed machine again but this time I did not go into X just stayed in RL3. Then ran bitbake perl, on a clean build dir. It is just about to finish building a few steps away but where I normally get the segfaults, it has not spit those out. There are no QA logs being generated either. So looks like it had/has something to do with running X, both systems are running nvidia graphics cards. The laptop has a new mobile one, borrowed an old one that is nouveau compatible. So both open and closed nvidia drivers were tried. But something when in the graphical environment is giving the segfault issues I have been seeing. I have not yet verified if killing X on the laptop builds and eliminates the issues as well. Will post back once I have built the kernel on both machines with no X running. There is a known issue w/ nvidia drivers, segfaulting and QEMU. Is something in perl (or elsewhere) trying to run qemu to finish up a task? --Mark Not that I can tell, but that does not mean it is not (still learning things), but possible one of threads is working on something perl related when it happens and I am not seeing it or realizing it. If you are willing to post the commands I could run to check, I can post the results. But when I do just a bitbake -c compile perl on a clean build dir all I would see was the segfault in dmesg and the results in QA log. Nothing would show up on the command line that was not in the QA log, after doing each step one by one. But it must be related to this known issue with nvidia. Should be a couple hours before both machines finish building the kernel and perl, will post the results after. But looks promising for my laptop so far as no segfaults yet. Borrowed machine is on to building the kernel now and nothing posted yet. Thank you for your response very appreciated. I will also read more about the issue you stated. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/17/2012 12:49 PM, j wrote: On 04/17/2012 12:34 PM, Mark Hatle wrote: On 4/17/12 2:09 PM, j wrote: On 04/17/2012 09:13 AM, J. L. wrote: snip http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel I went for a build on the borrowed machine again but this time I did not go into X just stayed in RL3. Then ran bitbake perl, on a clean build dir. It is just about to finish building a few steps away but where I normally get the segfaults, it has not spit those out. There are no QA logs being generated either. So looks like it had/has something to do with running X, both systems are running nvidia graphics cards. The laptop has a new mobile one, borrowed an old one that is nouveau compatible. So both open and closed nvidia drivers were tried. But something when in the graphical environment is giving the segfault issues I have been seeing. I have not yet verified if killing X on the laptop builds and eliminates the issues as well. Will post back once I have built the kernel on both machines with no X running. There is a known issue w/ nvidia drivers, segfaulting and QEMU. Is something in perl (or elsewhere) trying to run qemu to finish up a task? --Mark Not that I can tell, but that does not mean it is not (still learning things), but possible one of threads is working on something perl related when it happens and I am not seeing it or realizing it. If you are willing to post the commands I could run to check, I can post the results. But when I do just a bitbake -c compile perl on a clean build dir all I would see was the segfault in dmesg and the results in QA log. Nothing would show up on the command line that was not in the QA log, after doing each step one by one. But it must be related to this known issue with nvidia. Should be a couple hours before both machines finish building the kernel and perl, will post the results after. But looks promising for my laptop so far as no segfaults yet. Borrowed machine is on to building the kernel now and nothing posted yet. Thank you for your response very appreciated. I will also read more about the issue you stated. From what I am reading about this is its related to libgl. But on the machine I borrowed I used nouveau driver's which uses the libgl that is expected not the nvidia's supplied version. So maybe that is not fully it. But still all seems related to being in an X environment for me when building. Which is at least easy to work around. Will post if it segfaults again on either machine once they are done. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/17/2012 01:17 PM, j wrote: On 04/17/2012 12:49 PM, j wrote: On 04/17/2012 12:34 PM, Mark Hatle wrote: On 4/17/12 2:09 PM, j wrote: On 04/17/2012 09:13 AM, J. L. wrote: snip http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel I went for a build on the borrowed machine again but this time I did not go into X just stayed in RL3. Then ran bitbake perl, on a clean build dir. It is just about to finish building a few steps away but where I normally get the segfaults, it has not spit those out. There are no QA logs being generated either. So looks like it had/has something to do with running X, both systems are running nvidia graphics cards. The laptop has a new mobile one, borrowed an old one that is nouveau compatible. So both open and closed nvidia drivers were tried. But something when in the graphical environment is giving the segfault issues I have been seeing. I have not yet verified if killing X on the laptop builds and eliminates the issues as well. Will post back once I have built the kernel on both machines with no X running. There is a known issue w/ nvidia drivers, segfaulting and QEMU. Is something in perl (or elsewhere) trying to run qemu to finish up a task? --Mark Not that I can tell, but that does not mean it is not (still learning things), but possible one of threads is working on something perl related when it happens and I am not seeing it or realizing it. If you are willing to post the commands I could run to check, I can post the results. But when I do just a bitbake -c compile perl on a clean build dir all I would see was the segfault in dmesg and the results in QA log. Nothing would show up on the command line that was not in the QA log, after doing each step one by one. But it must be related to this known issue with nvidia. Should be a couple hours before both machines finish building the kernel and perl, will post the results after. But looks promising for my laptop so far as no segfaults yet. Borrowed machine is on to building the kernel now and nothing posted yet. Thank you for your response very appreciated. I will also read more about the issue you stated. From what I am reading about this is its related to libgl. But on the machine I borrowed I used nouveau driver's which uses the libgl that is expected not the nvidia's supplied version. So maybe that is not fully it. But still all seems related to being in an X environment for me when building. Which is at least easy to work around. Will post if it segfaults again on either machine once they are done. My borrowed machine segfaulted while finishing building perl. So I guess that had nothing to do with the segfault issues. I ended up with the same qa.log output and same type of output on dmesg relating to libc and ld again. Laptop no X on that segfaulted in the normal places Should I try installing Ubuntu 10.04 on the borrowed machine and seeing if the OS works on that machine? I am still lost as nothing seems to really be telling me what is segfaulting. The rest of the logs basically look the same as the series I posted earlier. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/17/2012 02:16 PM, j wrote: On 04/17/2012 01:17 PM, j wrote: On 04/17/2012 12:49 PM, j wrote: On 04/17/2012 12:34 PM, Mark Hatle wrote: On 4/17/12 2:09 PM, j wrote: On 04/17/2012 09:13 AM, J. L. wrote: snip http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel I went for a build on the borrowed machine again but this time I did not go into X just stayed in RL3. Then ran bitbake perl, on a clean build dir. It is just about to finish building a few steps away but where I normally get the segfaults, it has not spit those out. There are no QA logs being generated either. So looks like it had/has something to do with running X, both systems are running nvidia graphics cards. The laptop has a new mobile one, borrowed an old one that is nouveau compatible. So both open and closed nvidia drivers were tried. But something when in the graphical environment is giving the segfault issues I have been seeing. I have not yet verified if killing X on the laptop builds and eliminates the issues as well. Will post back once I have built the kernel on both machines with no X running. There is a known issue w/ nvidia drivers, segfaulting and QEMU. Is something in perl (or elsewhere) trying to run qemu to finish up a task? --Mark Not that I can tell, but that does not mean it is not (still learning things), but possible one of threads is working on something perl related when it happens and I am not seeing it or realizing it. If you are willing to post the commands I could run to check, I can post the results. But when I do just a bitbake -c compile perl on a clean build dir all I would see was the segfault in dmesg and the results in QA log. Nothing would show up on the command line that was not in the QA log, after doing each step one by one. But it must be related to this known issue with nvidia. Should be a couple hours before both machines finish building the kernel and perl, will post the results after. But looks promising for my laptop so far as no segfaults yet. Borrowed machine is on to building the kernel now and nothing posted yet. Thank you for your response very appreciated. I will also read more about the issue you stated. From what I am reading about this is its related to libgl. But on the machine I borrowed I used nouveau driver's which uses the libgl that is expected not the nvidia's supplied version. So maybe that is not fully it. But still all seems related to being in an X environment for me when building. Which is at least easy to work around. Will post if it segfaults again on either machine once they are done. My borrowed machine segfaulted while finishing building perl. So I guess that had nothing to do with the segfault issues. I ended up with the same qa.log output and same type of output on dmesg relating to libc and ld again. Laptop no X on that segfaulted in the normal places Should I try installing Ubuntu 10.04 on the borrowed machine and seeing if the OS works on that machine? I am still lost as nothing seems to really be telling me what is segfaulting. The rest of the logs basically look the same as the series I posted earlier. Well finally caught what I think is the package the segfault kicks on expat. Though not sure what I should look for to be able to sort it out but will see where I get. Though I still get the gcc and bash messages in the QA log. If anyone is willing to share some info on what or how I can figure out how to find what causes the segfault in the recipe or if I am even catching the correct one. Thank you ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On Tue, Apr 17, 2012 at 5:37 PM, j vwyodap...@gmail.com wrote: Well finally caught what I think is the package the segfault kicks on expat. Though not sure what I should look for to be able to sort it out but will see where I get. Though I still get the gcc and bash messages in the QA log. If anyone is willing to share some info on what or how I can figure out how to find what causes the segfault in the recipe or if I am even catching the correct one. you are not giving out enough information. Looking at dmesg is not going to give much info if ld segfaults which I assume is cross ld here then the corresponding recipe should fail and then you should look in the build of that package and the commands causing the segfaults should be in log.do_compile or log.do_install. Thanks -Khem ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/17/2012 10:30 PM, Khem Raj wrote: On Tue, Apr 17, 2012 at 5:37 PM, jvwyodap...@gmail.com wrote: Well finally caught what I think is the package the segfault kicks on expat. Though not sure what I should look for to be able to sort it out but will see where I get. Though I still get the gcc and bash messages in the QA log. If anyone is willing to share some info on what or how I can figure out how to find what causes the segfault in the recipe or if I am even catching the correct one. you are not giving out enough information. Looking at dmesg is not going to give much info if ld segfaults which I assume is cross ld here then the corresponding recipe should fail and then you should look in the build of that package and the commands causing the segfaults should be in log.do_compile or log.do_install. Thanks -Khem ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel See thats the thing no recipe is failing but the system segfaults. The resulting images have had quirks which is what led me to trying to sort out the segfault issue. Sorry to sound so dumb but if there is no recipe failing and 2 separate systems are segfaulting in similar manners and both result with not fully functioning images/packages where else can I look for info? I posted all the logs to one of the builds, and the QA log seems to be the only thing really spitting out anything. I am open to trying and or sharing any and all relevant info to help sort it out or get me on track to sorting it out. Thank you for all the continued effort. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? You've tried different Operating Systems, but one would assume that this is all on the same hardware? Have you tried a different build host (i.e. hardware/box)? -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? You've tried different Operating Systems, but one would assume that this is all on the same hardware? Have you tried a different build host (i.e. hardware/box)? sadly the only other hardware I have is to old to try a build on. Would take me weeks to get a complete image. So this could be a hardware problem on my end? If so any chance you know what I could search for in logs or anything like that to try and track down what on the hardware side is causing it? Thanks a bunch for your reply though is not something I took in to account, reason being is I can build the gumstix overo chain (oe-classic I believe it is) on the same hardware with out running into this issue. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? You've tried different Operating Systems, but one would assume that this is all on the same hardware? Have you tried a different build host (i.e. hardware/box)? Also it seems to happen around when bitbake starts building gcc-4.5 from a fresh install that is why I posted the QA info about it. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [oe-core] ld segfault cant figure it out
On 2012-04-16 16:32, j wrote: On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? You've tried different Operating Systems, but one would assume that this is all on the same hardware? Have you tried a different build host (i.e. hardware/box)? sadly the only other hardware I have is to old to try a build on. Would take me weeks to get a complete image. So this could be a hardware problem on my end? If so any chance you know what I could search for in logs or anything like that to try and track down what on the hardware side is causing it? Random errors like this always make me question the hardware. The fact that it can work fine in one setup but not another reinforces that. It might not be the case, but I think you'll have to check it out. Thanks a bunch for your reply though is not something I took in to account, reason being is I can build the gumstix overo chain (oe-classic I believe it is) on the same hardware with out running into this issue. --
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/16/2012 03:41 PM, Gary Thomas wrote: On 2012-04-16 16:32, j wrote: On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? You've tried different Operating Systems, but one would assume that this is all on the same hardware? Have you tried a different build host (i.e. hardware/box)? sadly the only other hardware I have is to old to try a build on. Would take me weeks to get a complete image. So this could be a hardware problem on my end? If so any chance you know what I could search for in logs or anything like that to try and track down what on the hardware side is causing it? Random errors like this always make me question the hardware. The fact that it can work fine in one setup but not another reinforces that. It might not be the case, but I think you'll have to check it out. Thanks a bunch for your reply though is not something I took in to account, reason being is I can build the gumstix overo chain (oe-classic I believe it is) on the same hardware
Re: [oe] [oe-core] ld segfault cant figure it out
On 04/16/2012 03:34 PM, j wrote: On 04/16/2012 03:28 PM, Gary Thomas wrote: On 2012-04-16 16:11, j wrote: On 04/13/2012 03:50 PM, j wrote: 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? I have now tried the build on 3 different OS's the most recent being Arch. All give the same QA log's and all give me segfaults. That are all basically close to the same errors just differing libc versions. I have tried Ubuntu 10.04 11.04 Fedora 16 and now Arch. What is causing the segfaults? Is it what is in the QA log? Most current [ 6433.379801] ld[22955]: segfault at 403 ip 7f703ddcc435 sp 7fffb0bd9f50 error 4 in libc-2.15.so[7f703dd85000+197000] [ 6444.526227] ld[31806]: segfault at 403 ip 7f0dffc51435 sp 7fffc0a990d0 error 4 in libc-2.15.so[7f0dffc0a000+197000] 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' 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' bash-4.2: bash: Found a reference to /usr/ in /home/gusterson/OpenEmbed/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 The only reason I am concerned with this and it may be un related is that every time I build task-native-sdk it does not build a working sdk for my device. BB-xm. Yes I know I can install one from the repo, but I want to figure out what is wrong with building one for me. Does anyone have input, advice something? You've tried different Operating Systems, but one would assume that this is all on the same hardware? Have you tried a different build host (i.e. hardware/box)? Also it seems to happen around when bitbake starts building gcc-4.5 from a fresh install that is why I posted the QA info about it. Well just built systemd-image got some more info from the QA log. seems that during the initial build with GCC and libtool it throws the segfaults. Then as the rest of build goes others have issues. I am going to try and rebuild the packages I think are causing this step by step and see if something sticks out during the process that might lead to a way to sort out the issue. I will start on a fresh boot of the system as well to make sure I can catch all the variables hopefully that are causing it. I also noticed some patches to perl I think it was that were ld related when 11.04 came out,
