From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Trying and Failing to enable Java with GCC 4.3.3
Date: Wed, 3 Mar 2010 21:23:48 -0800 [thread overview]
Message-ID: <19c1b8a91003032123t4e402cb0u8db75a6862dca799@mail.gmail.com> (raw)
In-Reply-To: <4CF74675-86F3-45C9-A837-5D5A3489F2A5@kaon.com>
On Wed, Mar 3, 2010 at 9:19 AM, Joshua Smith <jesmith@kaon.com> 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
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
next prev parent reply other threads:[~2010-03-04 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 16:20 Trying and Failing to enable Java with GCC 4.3.3 Joshua Smith
2010-03-03 17:19 ` Joshua Smith
2010-03-04 5:23 ` Khem Raj [this message]
2010-03-04 14:41 ` Joshua Smith
2010-03-05 2:39 ` Khem Raj
2010-03-05 3:27 ` Joshua Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19c1b8a91003032123t4e402cb0u8db75a6862dca799@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.