Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1279] New: Buildroot compiled Busybox and Coreutils LFS issues
Date: Sat, 13 Mar 2010 14:04:51 +0000 (UTC)	[thread overview]
Message-ID: <bug-1279-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1279

           Summary: Buildroot compiled Busybox and Coreutils LFS issues
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: richard-bugs at nod.at
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=1225)
 --> (https://bugs.busybox.net/attachment.cgi?id=1225)
Buildroot configuration

I set up a very basic root filesystem with large file support (BR2_LARGEFILE=y)
using Buildroot.
But ls from both Busybox and Coreutils fails on large directories.
In my case /mnt, which is a 1.4TB cifs share. On a smaller(~100GB) one it works
fine.

Strace shows that ls fires fstat() instead of fstat64().
So I wore a small testtool, which uses the fstat() library call.
It worked perfectly. According to strace my tool uses fstat64().

It seems that Buildroot messes something up while building Busybox and
Coreutils with large file support.

Config files, strace logs and my testtool are attached.

I reproduced this issue with Buildroot 2010.02 and snapshot from yesterday.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-03-13 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-13 14:04 bugzilla at busybox.net [this message]
2010-03-13 14:05 ` [Buildroot] [Bug 1279] Buildroot compiled Busybox and Coreutils LFS issues bugzilla at busybox.net
2010-03-13 14:06 ` bugzilla at busybox.net
2010-03-13 14:06 ` bugzilla at busybox.net
2010-03-13 14:07 ` bugzilla at busybox.net
2010-03-13 14:07 ` bugzilla at busybox.net
2010-03-13 14:07 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2013-11-28 18:30 ` bugzilla at busybox.net

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=bug-1279-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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