From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot 2012.11 large file support
Date: Wed, 12 Dec 2012 18:32:04 +0100 [thread overview]
Message-ID: <20121212183204.718be669@skate> (raw)
In-Reply-To: <874njrnroe.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 12 Dec 2012 17:47:29 +0100, Peter Korsgaard wrote:
> 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?
!largefile build is OK if we pass $(DISABLE_LARGEFILE) to gcc1 and gcc2
configure steps, so it solves the build problem. I haven't done more
testing though (testing the generated code, building with largefile
enabled, etc.).
That said, doesn't --disable-largefile disables largefile support at
the level of gcc itself, rather than taking into account the fact that
largefile support is not available on the target? Of course, it has the
consequence that _FILE_OFFSET_BITS is no longer defined to 64 in
auto-conf.h, which works around the problem. But gcc (the host
binary) should be capable of being built with largefile support on a 32
bits host, even if the 32 bits target has no largefile support.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-12 17:32 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
2012-12-12 17:32 ` Thomas Petazzoni [this message]
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=20121212183204.718be669@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.