From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot internal arm toolchain: gcc-final fails with supposedly large-file support
Date: Tue, 13 Aug 2013 09:05:57 +0200 [thread overview]
Message-ID: <20130813090557.5b35c25a@skate> (raw)
In-Reply-To: <52090BC7.5020500@mind.be>
Dear Arnout Vandecappelle,
On Mon, 12 Aug 2013 18:22:31 +0200, Arnout Vandecappelle wrote:
> On 29/07/13 14:06, Thomas De Schampheleire wrote:
> > So maybe it is build-machine related? Or depending on if some host
> > package is installed or not?
> > Would it help if I send a build log?
> > If I have time, I can try to look into it myself, but not right now...
>
> I you could just start a clean build of this .config in a different O=
> directory, we can see if it is build machine related or not... What kind
> of build machine do you have?
I *think* that the problem only happens on a 32 bits build machine.
As Thomas noticed the problem has already been fixed by
7fc685c9e0c9479365ca44158c1e928e57e391a4 in the master branch.
Thanks,
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:[~2013-08-13 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 10:25 [Buildroot] buildroot internal arm toolchain: gcc-final fails with supposedly large-file support Thomas De Schampheleire
2013-07-29 11:08 ` Thomas De Schampheleire
2013-07-29 11:35 ` Samuel Martin
2013-07-29 11:39 ` Thomas Petazzoni
2013-07-29 12:06 ` Thomas De Schampheleire
2013-08-12 16:22 ` Arnout Vandecappelle
2013-08-12 19:24 ` Thomas De Schampheleire
2013-08-13 7:05 ` 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=20130813090557.5b35c25a@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 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.