All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot internal arm toolchain: gcc-final fails with supposedly large-file support
Date: Mon, 12 Aug 2013 21:24:37 +0200	[thread overview]
Message-ID: <CAAXf6LWiPuamB03YWL5BT9jiDEiOu+O38T5vHm0qU38Eyo6qNg@mail.gmail.com> (raw)
In-Reply-To: <52090BC7.5020500@mind.be>

Hi Arnout,

Op 12-aug.-2013 20:45 schreef "Arnout Vandecappelle" <arnout@mind.be> het
volgende:
>
> 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?

Meanwhile, Francois Perrad also noticed this issue and submitted a patch
for it, which has been applied. Problem fixed...
(Don't have the commit id at hand, sorry)

Best regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130812/86e49f13/attachment.html>

  reply	other threads:[~2013-08-12 19:24 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 [this message]
2013-08-13  7:05           ` Thomas Petazzoni

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=CAAXf6LWiPuamB03YWL5BT9jiDEiOu+O38T5vHm0qU38Eyo6qNg@mail.gmail.com \
    --to=patrickdepinguin+buildroot@gmail.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.