From: "Kirill A. Shutemov" <k.shutemov@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fcntl64 fix
Date: Tue, 20 Mar 2007 21:34:42 +0200 [thread overview]
Message-ID: <20070320193442.GA11933@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0703201358190.12505@trantor.stuart.netsweng.com>
[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]
On [Tue, 20.03.2007 14:03], Stuart Anderson wrote:
> On Tue, 20 Mar 2007, Kirill A. Shutemov wrote:
>
> >>What are you using as a test app?
> >
> >I got error when runing Debian's apt-get and tried to fix it.
>
> OK, that's what got me started on this one, but I switched to using the
> ltp-kernel-test package for a more comprehensive set of tests once I got
> past that first eabi structure change.
>
> >>I think that remapping the constants
> >>is needed, but I'm just curious how we seem to be coming up with different
> >>parts of the fix when we have the same target/host combination.
> >
> >I'm not sure that I understand you...
>
> On the arm/x86_64 combination, I think the host & target cmd values are
> the same, so the remapping is a noop.
No. Remap is needed:
$ uname -m; echo -e '#include <fcntl.h>\nF_GETLK64' | cpp | tail -1
x86_64
5
$ uname -m; echo -e '#include <fcntl.h>\nF_GETLK64' | cpp | tail -1
armv5l
12
Same for F_SETLK64 and F_SETLKW64.
> It may be needed for other
> combinations though. Some architectures have very different values for
> constants like this in their ABI.
>
> I was trying to understand how your fix made apt-get/dpkg happy, or if
> you were just using a different app that was hitting a different case
> for fcntl().
>
>
> Stuart
>
> Stuart R. Anderson anderson@netsweng.com
> Network & Software Engineering http://www.netsweng.com/
> 1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
> BD03 0A62 E534 37A7 9149
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Regards, Kirill A. Shutemov
+ Belarus, Minsk
+ Velesys LLC, http://www.velesys.com/
+ ALT Linux Team, http://www.altlinux.com/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-20 19:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 21:53 [Qemu-devel] [PATCH] fcntl64 fix Kirill A. Shutemov
2007-03-19 17:13 ` Thiemo Seufer
2007-03-19 17:48 ` Stuart Anderson
2007-03-20 6:46 ` Stuart Anderson
2007-03-20 11:43 ` Kirill A. Shutemov
[not found] ` <Pine.LNX.4.64.0703200954000.12505@trantor.stuart.netsweng.com>
2007-03-20 13:59 ` Kirill A. Shutemov
2007-03-20 16:54 ` Stuart Anderson
2007-03-20 17:11 ` Kirill A. Shutemov
2007-03-20 18:03 ` Stuart Anderson
2007-03-20 19:34 ` Kirill A. Shutemov [this message]
2007-03-20 20:26 ` Stuart Anderson
2007-03-20 21:32 ` Stuart Anderson
2007-03-20 21:40 ` Paul Brook
2007-03-20 21:47 ` Thiemo Seufer
2007-03-20 22:56 ` Kirill A. Shutemov
2007-03-20 22:59 ` Kirill A. Shutemov
2007-03-21 13:49 ` Stuart Anderson
2007-03-20 23:05 ` Stuart Anderson
2007-03-20 23:10 ` Kirill A. Shutemov
2007-03-20 23:11 ` Kirill A. Shutemov
2007-03-20 23:43 ` Paul Brook
2007-03-21 13:50 ` Stuart Anderson
2007-03-22 14:23 ` Kirill A. Shutemov
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 21:48 Kirill A. Shutemov
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=20070320193442.GA11933@localhost.localdomain \
--to=k.shutemov@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).