I can now configure my new recipe without failure. I don't understand why it made a difference, but I added the line:
SECTION = "console" to my recipe (since this is going to be a userspace application run from the console). After that change the configure step works without error; ld finds crt1.o without issue. Anybody know why this would help? However, I am still having my original build issue in which my application isn't finding the correct system header files. sysroot=/media/sda3/stuff/tmp/sysroots/armv5te-angstrom-linux-gnueabi, but the patched kernel for the SAM9x5 is located at /media/sda3/stuff/tmp/sysroots/at91sam9x5ek-angstrom-linux-gnueabi. I tried setting: EXTRA_OECONF = "--sysroot=/media/sda3/stuff/tmp/sysroots/at91sam9x5ek-angstrom-linux-gnueabi" in my recipe, but I discovered that my configure doesn't accept --sysroot as an option. It looks like I need to modify configure.ac for my application to add --sysroot as an option. So far, I haven't been able to decipher the Autotools instructions enough to figure out how to do this. Any help would be greatly appreciated. Thanks again to everyone who has helped me get this far along. Thanks, Bryan -----Original Message----- From: angstrom-distro-devel-boun...@linuxtogo.org [mailto:angstrom-distro-devel-boun...@linuxtogo.org] On Behalf Of Gary Thomas Sent: Wednesday, April 04, 2012 12:42 PM To: angstrom-distro-devel@linuxtogo.org Subject: Re: [Angstrom-devel] Problems using autotools for new recipe On 2012-04-04 10:34, Khem Raj wrote: > On Tue, Apr 3, 2012 at 7:12 AM, Bryan Evenson<beven...@melinkcorp.com> wrote: >> I did a search, and it looks like crt1.o is under >> /media/sda3/stuff/tmp/sysroots/armv5te-angstrom-linux-gnueabi/usr/lib/. So >> I'm assuming I need to change the sysroot in my Bitbake recipe. I've tried >> figuring out how to do that in the past, but I haven't found a clear >> explanation. How do I do that? >> > > no it should be fine since compiler should have searched for it in > usr/lib under the sysroot so I dont know whats going on I often track these things down by running strace, e.g. % strace -f -o /tmp/xx.bb bitbake WHATEVER % grep crt1.o /tmp/xx.bb It should be obvious where the compiler thinks it should be, vs where it is. n.b. this is a pretty "heavy hammer" approach, but quick & easy to try :-) >> -----Original Message----- >> From: angstrom-distro-devel-boun...@linuxtogo.org >> [mailto:angstrom-distro-devel-boun...@linuxtogo.org] On Behalf Of Khem Raj >> Sent: Tuesday, April 03, 2012 9:46 AM >> To: Discussion of the angstrom distribution development >> Subject: Re: [Angstrom-devel] Problems using autotools for new recipe >> >> On Tue, Apr 3, 2012 at 5:26 AM, Bryan Evenson<beven...@melinkcorp.com> >> wrote: >>> --sysroot=/media/sda3/stuff/tmp/sysroots/armv5te- >>> >>> angstrom-linux-gnueabi >> >> your sysroot is pointing to >> --sysroot=/media/sda3/stuff/tmp/sysroots/armv5te-angstrom-linux-gnueabi >> and I hope under that dir you have crt1.o -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
