Oh, sorry about that. I've attached the do_configure log for gcc_cross. Doesn't look too helpful to me, but what do I know? If you meant some other configure log, let me know!
In case it helps: before trying to build gcj inside OE, I was trying to build a native GCC compiler on the target machine (TouchBook, based on the Beagleboard), and I got this same error when I tried configuring with --disable-shared (with --enabled-shared I had other problems). Thanks. -Joshua On Mar 4, 2010, at 12:23 AM, Khem Raj wrote: > On Wed, Mar 3, 2010 at 9:19 AM, Joshua Smith <[email protected]> wrote: >> Update: I dug around in the log files and I think I have a more root cause >> of this error. >> >> configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. >> >> I've attached the whole log of the failing build. >> >> Any hints? >> >> On Mar 3, 2010, at 11:20 AM, Joshua Smith wrote: >> >>> Hello, >>> >>> I'm new to OE. I'm trying to get GCJ compiled for the TouchBook (an >>> ARM-based tablet). After some searching and trial-and-error, I figured out >>> that I need to add: >>> >>> JAVA_arm = ",java" to recipies/gcc-4.3.3.inc >>> >>> But now I'm getting an error when it tries to build gcc-cross-4.3.3: >>> >>> make[4]: Entering directory >>> `/OE/build/tmp/work/armv7a-angstrom-linux-gnueabi/gcc-cross-4.3.3-r7.1/gcc-4.3.3/build.i686-linux.arm-angstrom-linux-gnueabi/64/zlib' >>> make[4]: *** No rule to make target `all'. Stop. >>> make[4]: Leaving directory >>> `/OE/build/tmp/work/armv7a-angstrom-linux-gnueabi/gcc-cross-4.3.3-r7.1/gcc-4.3.3/build.i686-linux.arm-angstrom-linux-gnueabi/64/zlib' >>> make[3]: *** [multi-do] Error 1 >>> make[3]: Leaving directory >>> `/OE/build/tmp/work/armv7a-angstrom-linux-gnueabi/gcc-cross-4.3.3-r7.1/gcc-4.3.3/build.i686-linux.arm-angstrom-linux-gnueabi/zlib' >>> make[2]: *** [all-multi] Error 2 >>> make[2]: Leaving directory >>> `/OE/build/tmp/work/armv7a-angstrom-linux-gnueabi/gcc-cross-4.3.3-r7.1/gcc-4.3.3/build.i686-linux.arm-angstrom-linux-gnueabi/zlib' >>> make[1]: *** [all-zlib] Error 2 >>> >>> (I can give you more of the log if it would help, but this is the first >>> error) >>> >>> I can see why adding Java would cause GCC to need zlib when maybe it didn't >>> before. But I don't know what to change to get zlib configured as part of >>> the gcc build process. > > for configure errors its better to post config.log which is generated > in the build tree. Thats where we can find the cause of error. > do_compile log wont help. > > >>> >>> Help? >>> >>> -Joshua Smith >>> >> >> _______________________________________________ >> Openembedded-devel mailing list >> [email protected] >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel >> >> > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
log.do_configure.17055
Description: Binary data
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
