On 12/21/18 10:48 AM, John Paul Adrian Glaubitz wrote:
> The patch contains a bogus hunk at the bottom, cleaned up patch attached.
And this time, I messed up the formatting. *sigh*
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universit
On 12/21/18 10:48 AM, John Paul Adrian Glaubitz wrote:
> On 12/21/18 10:22 AM, John Paul Adrian Glaubitz wrote:
>> The attached patch uses the correct fnctl constants for sparc64 to fix
>> the problem. I haven't checked the other architectures but it may be
>> worth to verify that the other non-x86
On 12/21/18 10:22 AM, John Paul Adrian Glaubitz wrote:
> The attached patch uses the correct fnctl constants for sparc64 to fix
> the problem. I haven't checked the other architectures but it may be
> worth to verify that the other non-x86 architectures are using the correct
> constansts as well.
Source: rustc
Version: 1.31.0+dfsg1-2
Severity: normal
Tags: patch upstream
User: debian-sp...@lists.debian.org
Usertags: sparc64
Hello!
The fnctl constants used by the file-locking API are hard-coded in the
code instead of using the libc crate. This causes the compiler to emit
the wrong fnctl fo
4 matches
Mail list logo