Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Broken pread() on ARM
Date: Wed, 05 Feb 2014 08:49:08 +0100	[thread overview]
Message-ID: <87siry2e4r.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAKgsxVSJAW73vXdkKQFLZOYp3qzZm9qwF5+p0NUtUUSnzsFZtQ@mail.gmail.com> (Justin Maggard's message of "Tue, 4 Feb 2014 16:21:01 -0800")

>>>>> "Justin" == Justin Maggard <jmaggard10@gmail.com> writes:

Hi,

 > Okay, it looks like some of the pread/pwrite changes that have made
 > their way into the uClibc 0.9.33 branch fail to consider some
 > architectures.  I have made a rather odd-looking change locally that
 > makes it work for me on my ARM platform, which uses _syscall6() for
 > pread() and pread64() if __UCLIBC_TRUNCATE64_HAS_4_ARGS__ is defined.
 > Would that be worth sending to the list, or would it be better to fix
 > it some other way?

The best approach would be to get it fixed in uClibc git (and preferably
to get them to finally release 0.9.33.3).

This particular issue also fixed on the uClibc master branch (E.G. what
should become 0.9.34) - But when I had a look at it, it didn't seem
trivial to backport.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-05  7:49 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 [this message]
2014-02-07  1:54     ` Justin Maggard
2014-02-07  9:56       ` Peter Korsgaard
2014-02-05  7:47 ` 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=87siry2e4r.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