gnutls-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile testsuite failure (gnutls 3.0.1 and later) and armel and mipse


From: Nikos Mavrogiannopoulos
Subject: Re: guile testsuite failure (gnutls 3.0.1 and later) and armel and mipsel
Date: Mon, 07 Nov 2011 21:35:55 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20111010 Icedove/3.1.15

On 11/07/2011 09:31 PM, Ludovic Courtès wrote:

>>> Compile & run with -D_FILE_OFFSET_BITS=32 then -D_FILE_OFFSET_BITS=64:
>>>   32 -> 96
>>>   64 -> 120
>>> Problems arise when libguile is compiled, say, with _FILE_OFFSET_BITS=32
>>> whereas gnutls-guile is compiled with _FILE_OFFSET_BITS=64.
>>
>> So as I understand it, it doesn't really seem like a gnutls or guile
>> issue.
> 
> Well, yes and no.  Application programmers are free to choose whichever
> _FILE_OFFSET_BITS they may want.  So it’s a Guile problem in the sense
> that libguile’s API should match its ABI, and thus should be independent
> of the _FILE_OFFSET_BITS value its users choose for themselves.
> 
> That’s how it was fixed in Guile 2.0:
> 
>   
> http://git.savannah.gnu.org/cgit/guile.git/commit/?id=f1ce9199335bebab1a62286ac965f33dc91ca97f

I've reported it to gnulib because adding unrelated modules shouldn't
enable 64-bit support implicitly anyway.

regards,
Nikos



reply via email to

[Prev in Thread] Current Thread [Next in Thread]