From: Scott Dudley <scott@telesoft.com>
To: buildroot@busybox.net
Subject: [Buildroot] What Version for Java Support
Date: Mon, 01 Nov 2010 11:28:40 -0700 [thread overview]
Message-ID: <4CCF06D8.3070406@telesoft.com> (raw)
I need a uClibc cross toolchain that supports Java (GCJ) for the 386 or
486 target on my x86_64 host. I tried buildroot-2010.08 but it wouldn't
build. Without tinkering, I tried the latest from git and everything
builds find. I tried setting the BR2_INSTALL_LIBGCJ variable in my
.config file but it appears to get removed when I run make and gcj
doesn't get compiled. Saw a thread that suggested Java support had been
or was going to be deprecated.
Can you tell me what the most current version of buildroot is that
supports gcj and will build on my 64-bit host?
Many thanks.
--
Scott Dudley
Senior Developer
Telesoft Corp. | 3443 N. Central Ave., 18th Floor | Phoenix, AZ, 85012
*o:* (602) 308-1115* *| *f:* (602) 308-1300 | *w:* www.telesoft.com
<http://www.telesoft.com/?utm_source=signature&utm_medium=email&utm_campaign=signature>
<http://www.telesoft.com/?utm_source=signature&utm_medium=email&utm_campaign=signature>
<http://www.telesoft.com/sites/default/files/go/signature.html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101101/4f28f9a9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sig-logo.png
Type: image/png
Size: 1902 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101101/4f28f9a9/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sig-right.png
Type: image/png
Size: 24470 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101101/4f28f9a9/attachment-0003.png>
reply other threads:[~2010-11-01 18:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CCF06D8.3070406@telesoft.com \
--to=scott@telesoft.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox