From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARM build error with llseek.c
Date: Fri, 16 May 2008 09:53:30 +0200 [thread overview]
Message-ID: <20080516075330.GA22291@mx.loc> (raw)
In-Reply-To: <326f33790805151641l495774fdpf0efe19c9f060135@mail.gmail.com>
On Thu, May 15, 2008 at 04:41:48PM -0700, Arun Reddy wrote:
>Thanks Chris,
>
>Looks like the issue was with LFS not being enabled in uclibc
>(CONFIG_UCLIBC_HAS_LFS) and also BusyBox not having
>BR2_PACKAGE_BUSYBOX_HIDE_OTHERS selected. I did a make clean for everything
>and rebuilt, and got past that error.
>
>I am fairly certain I understand why LFS needed to be enabled, because I was
>reading up on a couple threads online about llseek.c being used for large
>file support in general, while lseek.c is used for small files. I want LFS
>for my purposes, and it is possible that by not selecting LFS in the uclibc
>menuconfig, that a specific function or variable wasn't defined correctly in
>a header file used by llseek.c, and therefore it couldn't compile correctly.
>This is of course my best assumption.
>
>As for selecting BusyBox's hide others option, I am unsure as to why that
>works, but found it here as a suggestion.
It works because if you enable it then you use busybox and not the big
util-linux.
As for your trouble with toggling LFS and other settings. This is
believed to be fixed in my tree, i.e. the user doesn't have to take care
of doing make uclibc-clean gcc-clean et al when she toggles LARGEFILE,
SJLJ or chooses to add or remove support for a language in her
cross-compiler or stuff like that.
PS: It would be helpful if you could send your errors to the list (as
text, of course) and not send a link to some picture of the error
message. TIA
next prev parent reply other threads:[~2008-05-16 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 22:49 [Buildroot] ARM build error with llseek.c Arun Reddy
2008-05-08 23:11 ` hartleys
2008-05-08 23:24 ` Arun Reddy
[not found] ` <1CF6EDDF0820924DA43C9A52FE7325950B4DAA2E@MI8NYCMAIL17.Mi8.com>
[not found] ` <326f33790805081812sc3b8d29v948f331f7fe84653@mail.gmail.com>
2008-05-09 1:13 ` Arun Reddy
2008-05-12 3:24 ` Arun Reddy
2008-05-15 23:20 ` Christopher Taylor
2008-05-15 23:41 ` Arun Reddy
2008-05-16 7:53 ` Bernhard Fischer [this message]
2008-05-16 15:31 ` Arun Reddy
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=20080516075330.GA22291@mx.loc \
--to=rep.dot.nop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox