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, 29 Jul 2013 14:06:31 +0200	[thread overview]
Message-ID: <CAAXf6LUib4JKaLQjzqicv3PbDhP6ZAT-ZZVFcxRNmugAgA13ZQ@mail.gmail.com> (raw)
In-Reply-To: <20130729133930.09abcb5b@skate>

On Mon, Jul 29, 2013 at 1:39 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Samuel Martin,
>
> On Mon, 29 Jul 2013 13:35:41 +0200, Samuel Martin wrote:
>
>> >> The .config file is in attachment.
>> >> Largefile support is not enabled, yet for some reason gcc thinks it
>> >> is. I haven't been able to look into detail why this is so.
>> >
>> > For the record: just had the same type of problem with powerpc as well...
>>
>> Yesterday, I gave a run using your config and it worked fine here.
>
> I just built the following defconfig, and it build fine here:
>
> BR2_arm=y
>
> That said, I remember we had reports of similar problems some time ago,
> but I don't remember enough informations to find related e-mails on the
> list.

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...

Best regards,
Thomas

  reply	other threads:[~2013-07-29 12:06 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 [this message]
2013-08-12 16:22         ` Arnout Vandecappelle
2013-08-12 19:24           ` Thomas De Schampheleire
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=CAAXf6LUib4JKaLQjzqicv3PbDhP6ZAT-ZZVFcxRNmugAgA13ZQ@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.