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 12:03:41 +0100 [thread overview]
Message-ID: <20121212120341.69a89e93@skate> (raw)
In-Reply-To: <20121212120159.4292d70b@skate>
Dear Thomas Petazzoni,
On Wed, 12 Dec 2012 12:01:59 +0100, Thomas Petazzoni wrote:
>
> On Wed, 12 Dec 2012 11:16:28 +0100, Thomas Petazzoni wrote:
>
> > I haven't looked into them for now.
>
> Ok, a quick investigation shows that crtstuff.c includes auto-host.h,
> which contains _FILE_OFFSET_BITS. crtstuff.c is built for the target,
> and therefore should normally not include auto-host.h, as noted by the
> following comment:
>
> ==
> /* FIXME: Including auto-host is incorrect, but until we have
> identified the set of defines that need to go into auto-target.h,
> this will have to do. */
> #include "auto-host.h"
> ==
(sorry for not finishing the e-mail)
And this is causing problems for cross-compilation. For example:
http://www.archivum.info/gcc-patches at gcc.gnu.org/2005-11/00293/Patch-to-crtstuff.c-to-undefine-some-macros-after-auto-host.h.html.
According to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21481 it is
quite clear that crtstuff.c should not include auto-host.h, but
apparently, it is not that simple.
Thing that remains not understood is what change between 4.5 and 4.6
broke this.
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 11:03 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 [this message]
2012-12-12 12:47 ` Thomas Petazzoni
2012-12-12 16:47 ` Peter Korsgaard
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=20121212120341.69a89e93@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox