From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot 2012.11 large file support
Date: Wed, 12 Dec 2012 17:47:29 +0100 [thread overview]
Message-ID: <874njrnroe.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20121212134703.7461d9c7@skate> (Thomas Petazzoni's message of "Wed, 12 Dec 2012 13:47:03 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Dear Thomas Petazzoni,
Thomas> On Wed, 12 Dec 2012 12:03:41 +0100, Thomas Petazzoni wrote:
>> Thing that remains not understood is what change between 4.5 and 4.6
>> broke this.
Thomas> Apparently, what changed is that the gcc/configure.ac has gained a
Thomas> AC_SYS_LARGEFILE check:
Thomas> $ grep LARGEFILE toolchain/gcc-4.6.3/gcc/configure.ac
Thomas> AC_SYS_LARGEFILE
Thomas> $ grep LARGEFILE toolchain/gcc-4.5.4/gcc/configure.ac
Thomas> $
Thomas> On gcc >= 4.6, this means that a #define _FILE_OFFSET_BITS 64 is added
Thomas> to auto-host.h, which breaks the build of crtstuff.c for the target as
Thomas> uClibc headers warn that _FILE_OFFSET_BITS is set to 64 even though
Thomas> largefile support is not enabled.
Hmm, we already pass --disable-largefile to the gcc configure script,
except for the first 2 passes. Does it work if we add
$(DISABLE_LARGEFILE) to the gcc1 / gcc2 configure steps?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-12-12 16:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 12:35 [Buildroot] buildroot 2012.11 large file support Berns
2012-12-10 14:53 ` Willy Lambert
2012-12-10 19:20 ` Peter Korsgaard
2012-12-10 19:38 ` Willy Lambert
2012-12-10 20:38 ` Peter Korsgaard
2012-12-10 21:30 ` Willy Lambert
2012-12-10 22:05 ` Peter Korsgaard
2012-12-11 2:13 ` Willy Lambert
2012-12-11 7:04 ` Peter Korsgaard
2012-12-11 8:43 ` Willy Lambert
2012-12-11 9:09 ` Thomas Petazzoni
2012-12-12 1:04 ` Willy Lambert
2012-12-11 15:09 ` Willy Lambert
2012-12-11 16:10 ` Thomas Petazzoni
2012-12-12 0:35 ` Arnout Vandecappelle
2012-12-12 10:16 ` Thomas Petazzoni
2012-12-12 11:01 ` Thomas Petazzoni
2012-12-12 11:03 ` Thomas Petazzoni
2012-12-12 12:47 ` Thomas Petazzoni
2012-12-12 16:47 ` Peter Korsgaard [this message]
2012-12-12 17:32 ` Thomas Petazzoni
2012-12-12 20:15 ` Peter Korsgaard
2012-12-12 22:21 ` Thomas Petazzoni
2012-12-12 23:47 ` Arnout Vandecappelle
2012-12-13 10:45 ` Victor Hiairrassary
2012-12-13 10:55 ` Peter Korsgaard
2012-12-13 11:06 ` Arnout Vandecappelle
2012-12-13 11:28 ` Victor Hiairrassary
2012-12-12 9:20 ` Willy Lambert
2012-12-12 10:21 ` Fabio Porcedda
2012-12-11 9:30 ` Berns
2012-12-12 6:05 ` 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=874njrnroe.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.