From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-07-19
Date: Fri, 20 Jul 2012 10:15:33 +0200 [thread overview]
Message-ID: <20120720101533.54b4fcb3@skate> (raw)
In-Reply-To: <20120720100738.434746e8@skate>
Le Fri, 20 Jul 2012 10:07:38 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> It also means that having a multilib capable compiler is not a
> prerequisite of Buildroot on x86_64, at least to build Luajit for
Of course, as Maxime pointed me, I wanted to say:
It also means that having a multilib capable compiler is *NOW* a
prerequisite of Buildroot on x86_64, at least to build Luajit for
Which, of course is quite the opposite of what my initial e-mail was
saying. Thanks for pointing this!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-20 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2012-07-19 Thomas Petazzoni
2012-07-20 8:07 ` Thomas Petazzoni
2012-07-20 8:15 ` Thomas Petazzoni [this message]
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=20120720101533.54b4fcb3@skate \
--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