Your message dated Sat, 29 Oct 2005 10:36:39 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#335387: Perl, "use fcntl" reporting incorrect value for
F_SETLKW
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 23 Oct 2005 17:01:04 +0000
>From [EMAIL PROTECTED] Sun Oct 23 10:01:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from imf17aec.mail.bellsouth.net [205.152.59.65]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ETjDU-0007kK-00; Sun, 23 Oct 2005 10:01:04 -0700
Received: from ibm57aec.bellsouth.net ([65.7.241.41])
by imf17aec.mail.bellsouth.net with ESMTP
id <[EMAIL PROTECTED]>
for <[EMAIL PROTECTED]>; Sun, 23 Oct 2005 13:00:33 -0400
Received: from VaioLaptop ([65.7.241.41]) by ibm57aec.bellsouth.net
with SMTP
id <[EMAIL PROTECTED]>
for <[EMAIL PROTECTED]>; Sun, 23 Oct 2005 13:00:32 -0400
Message-ID: <[EMAIL PROTECTED]>
From: "John \(VMedia Admin\)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Perl, "use fcntl" reporting incorrect value for F_SETLKW
Date: Sun, 23 Oct 2005 12:55:53 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_017B_01C5D7D1.1A063BC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2670
Disposition-Notification-To: "John \(VMedia Admin\)" <[EMAIL PROTECTED]>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-2.2 required=4.0 tests=BAYES_44,HAS_PACKAGE,
HTML_40_50,HTML_MESSAGE autolearn=no
version=2.60-bugs.debian.org_2005_01_02
This is a multi-part message in MIME format.
------=_NextPart_000_017B_01C5D7D1.1A063BC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Package: perl
Version: 5.8.4
The value for F_SETLKW is coming up as "14" when my kernel is expecting =
"7".
I have tested this both under Kernel 2.4.26 and 2.6.8 -- same result.
I tested this with:
#!/usr/bin/perl
use Fcntl;
print "F_SETLKW: ".F_SETLKW."\n";
It returns "14" when a C program returns "7". This caused "byte range" =
locking to not work properly (it acts as if the full file locks.
I am guessing it has to do with the machine that the Debian distribution =
is created on having a different value than that of the destination box?
I don't have a solution for this as I am not experienced with making =
header files for Perl.
I could find no record of this issue anywhere. I wrote the usenet group =
for Perl and they indicated I should report this to you.
For more info, I am running Debian Sarge Stable -- fully updated =
recently (from woody). The problem is occurring on two different =
machines running two different kernels.
Linux mars.versimedia.com 2.6.8 #1 SMP Thu Oct 20 10:47:33 EDT 2005 i686 =
unknown
Linux europa 2.4.26 #1 SMP Thu May 27 14:47:32 EDT 2004 i686 unknown
------=_NextPart_000_017B_01C5D7D1.1A063BC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Package: perl</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Version: 5.8.4</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The value for F_SETLKW is coming up as =
"14" when my=20
kernel is expecting "7".</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have tested this both under Kernel =
2.4.26 and=20
2.6.8 -- same result.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I tested this with:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial =
size=3D2><STRONG>#!/usr/bin/perl</STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG></STRONG></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><STRONG>use =
Fcntl;<BR></STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG>print "F_SETLKW:=20
".F_SETLKW."\n";</STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It returns "14" when a C program =
returns "7". =20
This caused "byte range" locking to not work properly (it acts as if the =
full=20
file locks.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am guessing it has to do with the =
machine that=20
the Debian distribution is created on having a different value than that =
of the=20
destination box?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I don't have a solution for this as I =
am not=20
experienced with making header files for Perl.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I could find no record of this issue=20
anywhere. I wrote the usenet group for Perl and they indicated I =
should=20
report this to you.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>For more info, I am running Debian =
Sarge Stable --=20
fully updated recently (from woody). The problem is occurring on =
two=20
different machines running two different kernels.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Linux mars.versimedia.com 2.6.8 #1 SMP =
Thu Oct 20=20
10:47:33 EDT 2005 i686 unknown</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Linux europa 2.4.26 #1 SMP Thu May 27 =
14:47:32 EDT=20
2004 i686 unknown<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </DIV></FONT></BODY></HTML>
------=_NextPart_000_017B_01C5D7D1.1A063BC0--
---------------------------------------
Received: (at 335387-done) by bugs.debian.org; 29 Oct 2005 00:36:45 +0000
>From [EMAIL PROTECTED] Fri Oct 28 17:36:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from londo.c47.org [198.142.1.20] (mail)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EVeiD-0008PG-00; Fri, 28 Oct 2005 17:36:45 -0700
Received: from bod by londo.c47.org with local (Exim 3.36 #1 (Debian))
id 1EVei7-00074c-00; Sat, 29 Oct 2005 10:36:39 +1000
Date: Sat, 29 Oct 2005 10:36:39 +1000
From: Brendan O'Dea <[EMAIL PROTECTED]>
To: "John (VMedia Admin)" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#335387: Perl, "use fcntl" reporting incorrect value for
F_SETLKW
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
On Sun, Oct 23, 2005 at 12:55:53PM -0400, John (VMedia Admin) wrote:
>The value for F_SETLKW is coming up as "14" when my kernel is expecting "7".
The Debian perl package is compiled with large file support, which makes
F_SETLKW == F_SETLKW64 (14 on i386).
You need to use 64bit offsets in the structure... which is actually
kind of tricky, since there isn't 64bit integer support in the
package--there were build issues on some arches with use64bitall at the
time 5.8.0 was packaged--this will probably be added next time the ABI
changes (5.10.x).
For the moment, you can pack 32bit offsets on i386 with this completely
unportable hack:
my $lock = pack 's s Lx4 Lx4', F_WRLCK, SEEK_SET, $offset, $size;
--bod
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
