From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot questions
Date: Fri, 30 Jan 2009 08:05:45 +0100 [thread overview]
Message-ID: <87d4e5p92u.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090129151144.7e82de38@INDYZONE.dhcp.2wire.com> (Jackson Jones's message of "Thu\, 29 Jan 2009 15\:11\:44 -0800")
>>>>> "Jackson" == Jackson Jones <jjones@2wire.com> writes:
Hi,
Please mail the buildroot mailing list in the future so other people
can help as well.
Jackson> Peter,
Jackson> I had a couple of quick questions about build root. I am
Jackson> using the rc2 that is on the site. Is it a known bug that
Jackson> the libgcj does not build and causes a build error?
I'm afraid the java stuff may have bitrotted or is incomplete - I have
never tried it in all the time I have been working on buildroot, and I
don't ever remember any questions and/or patches about it on the list.
Anyone else?
Jackson> The other question I have is that I noticed that the ntpl
Jackson> library is not merged with uClibc, so selecting ntpl results
Jackson> in an error when the sysdep.h cannot be found. Is there a
Jackson> patch to add this in. I am trying to build a cross compiler
Jackson> to mipsel (for a broadcom chipset). We are currently using a
Jackson> glibc based toolchain (home grown), but want to switch to
Jackson> uClibc for the size advantage. Our platform is written in
Jackson> C/C++, but the application side is written in Java (compiled
Jackson> gcj).
The ntpl branch of uclibc is supposed to be merged real-soon-now, but
I don't actually know much more about it. I would suggest to stick to
the default linuxthreads for now.
Jackson> Thanks for you time,
You're welcome.
--
Bye, Peter Korsgaard
next parent reply other threads:[~2009-01-30 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090129151144.7e82de38@INDYZONE.dhcp.2wire.com>
2009-01-30 7:05 ` Peter Korsgaard [this message]
2009-02-21 17:12 [Buildroot] buildroot questions gsam at ixltc.com
2009-02-22 6:48 ` Peter Korsgaard
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=87d4e5p92u.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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