From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] jamvm: add depends on toolchain w/threads
Date: Wed, 1 Apr 2015 16:44:28 +0200 [thread overview]
Message-ID: <20150401164428.7fcc4854@free-electrons.com> (raw)
In-Reply-To: <CAMQcK5Lsur2cCryZ=fTGeeWRQzwCtaErkP-Of9auJ+-s6cHkEQ@mail.gmail.com>
Dear Ryan Barnett,
On Wed, 1 Apr 2015 09:28:12 -0500, Ryan Barnett wrote:
> > While running an autobuilder internally. It's a arm uclibc build
> > failure looking for pthreads.
>
> I am curious about the Buildroot autobuilders then if they don't have
> javac available on them to build.
>
> Thomas - are there autobuilders that have javac installed on them?
The autobuild-run script detects whether javac is available or not. If
it's not available, it makes sure to not attempt a build that has the
Buildroot packages that require javac to be installed.
On the Free Electrons build server, javac is not installed. On gcc75,
javac is installed.
See
http://git.buildroot.net/buildroot-test/tree/scripts/autobuild-run#n196
and
http://git.buildroot.net/buildroot-test/tree/scripts/autobuild-run#n339.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-01 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 15:54 [Buildroot] [PATCH 1/1] jamvm: add depends on toolchain w/threads Matt Weber
2015-03-26 18:16 ` Ryan Barnett
2015-03-26 18:52 ` Matthew Weber
2015-04-01 14:28 ` Ryan Barnett
2015-04-01 14:44 ` Thomas Petazzoni [this message]
2015-04-01 21:09 ` Matthew Weber
2015-04-01 21:43 ` Thomas Petazzoni
2015-04-01 21:48 ` Peter Korsgaard
2015-04-01 21:59 ` Thomas Petazzoni
2015-04-02 1:28 ` Matthew Weber
2015-04-02 8:04 ` Peter Korsgaard
2015-04-02 8:03 ` 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=20150401164428.7fcc4854@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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