Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Wood <ted@fgh.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Large File Support
Date: Tue, 11 Dec 2012 14:12:45 -0000	[thread overview]
Message-ID: <000901cdd7a9$98377ab0$c8a67010$@co.uk> (raw)

I hope this isn't an inappropriate place for this...

 

I'm  completely new to Embedded Linux, and am hoping to use Buildroot as the
basis for a new project.

 

I'm using the November 2012 release.

 

I'm trying to build for an i586 using the internal toolchain. The make fails
with the error "It appears you have defined _FILE_OFFSET_BITS=64.
Unfortunately uLibc was built without large file support"

 

I'm pretty sure I didn't request that when I was doing menuconfig. Web
search suggests that this problem has occurred elsewhere. There is an option
to select Large File Support under toolchain, but toggling it makes no
difference.

 

Anybody got any suggestions? 

 

T.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121211/da719da5/attachment.html>

             reply	other threads:[~2012-12-11 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 14:12 Ted Wood [this message]
2012-12-11 17:24 ` [Buildroot] Large File Support Samuel Martin

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='000901cdd7a9$98377ab0$c8a67010$@co.uk' \
    --to=ted@fgh.co.uk \
    --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