From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Broken pread() on ARM
Date: Wed, 05 Feb 2014 08:47:08 +0100 [thread overview]
Message-ID: <87wqha2e83.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAKgsxVRjJoJfk1UkXA4kMnt+TxtSfHgduyPjeF8gmrZTxFOvGw@mail.gmail.com> (Justin Maggard's message of "Tue, 4 Feb 2014 14:26:20 -0800")
>>>>> "Justin" == Justin Maggard <jmaggard10@gmail.com> writes:
> I'm using buildroot on a 32-bit ARM platform, and I have run into
> pread issues after recently switching from buildroot-2013.05 to
> buildroot-2013.11. In both cases I'm using a generated uClibc
> toolchain, and uClibc 0.9.33.2. Comparing the strace outputs of both,
> the offset shows up differently. As an extra data point, I tried the
> latest uClibc snapshot instead of 0.9.33.2, and it worked fine again.
> I see there are a number of extra uClibc patches that were added
> between 2013.05 and 2013.11. Perhaps we have just the right
> combination of backports to make some platforms work, while breaking
> others?
Yes, unfortunately. See
http://lists.busybox.net/pipermail/buildroot/2014-January/087050.html
for details.
uClibc upstream is unfortunately not very active at the moment, so for
2014.02 I will simply revert patch 14, 21, 32 and 54.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-02-05 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:26 [Buildroot] Broken pread() on ARM Justin Maggard
2014-02-05 0:21 ` Justin Maggard
2014-02-05 7:49 ` Peter Korsgaard
2014-02-07 1:54 ` Justin Maggard
2014-02-07 9:56 ` Peter Korsgaard
2014-02-05 7:47 ` Peter Korsgaard [this message]
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=87wqha2e83.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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