[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: safer way to use gnulib (for other MacOS X users)
From: |
Ben Abbott |
Subject: |
Re: safer way to use gnulib (for other MacOS X users) |
Date: |
Wed, 17 Mar 2010 17:30:07 -0400 |
On Wednesday, March 17, 2010, at 04:52PM, "Thomas Treichl" <address@hidden>
wrote:
>Am 17.03.10 21:31, schrieb Ben Abbott:
>> On Wednesday, March 17, 2010, at 03:28PM, "Thomas Treichl"<address@hidden>
>> wrote:
>>> Am 16.03.10 23:38, schrieb Ben Abbott:
>>>> On Mar 16, 2010, at 6:03 PM, John W. Eaton wrote:
>>>>
>>>>> On 16-Mar-2010, Ben Abbott wrote:
>>>>>
>>>>> | The dependencies of lex.cc aren't too many, so it finished quickly.
>>>>> Except for the one failure I always get with data.cc, all tests pass.
>>>>> |
>>>>> | Thanks again!
>>>>>
>>>>> OK, so now we finally have Octave+gnulib working on OS X, except that
>>>>> we need to do something about the possibility of sigemptyset and
>>>>> sigaddset being defined as preprocessor macros.
>>>>
>>>> I've attached a diff for others who may be building on MacOS X.
>>>>
>>>> Ben
>>>
>>> Hi Ben,
>>>
>>> I wasn't able to build a development snapshot for a very long time
>>> because of the gnulib problems. With your patch and a fresh gnulib
>>> checkout I get the following result on my 10.6 machine
>>>
>>> Summary:
>>> PASS 6374
>>> FAIL 0
>>>
>>> So wow, thanks to all developers!
>>>
>>> Thomas
>>
>> Thomas,
>>
>> I continue to encounter a failure in data.cc.
>>
>> 121>>>>> processing
>> /Users/bpabbott/Development/mercurial/local_clone/src/data.cc
>> 122 ***** assert(log2(complex(0,Inf)), Inf + log2(i));
>> 123 !!!!! test failed
>> 124 assert (log2 (complex (0, Inf)),Inf + log2 (i)) expected
>> 125 Inf + 2.266i
>> 126 but got
>> 127 Inf - NaNi
>> 128 NaNs don't match
>>
>> Using Apple's gcc-4.2.1, I've not been able to resolve this by changing the
>> optimization setting. Which gcc are you using and what level of optimization?
>>
>> Ben
>
>Oh yes, I remember I had similiar problems. I used these flags for CXX
>and for my g95 with low optimization -O instead of at least -O2 or even
>-O3 that I used before the change to gnulib. But I can check once again
>with higher optimization tomorrow
Are you really using g95 and not gfortran?
If so what version? and did you use it to build all the fortran dependencies?
Ben
- Re: safer way to use gnulib, (continued)
- Re: safer way to use gnulib, Ben Abbott, 2010/03/16
- Re: safer way to use gnulib, Ben Abbott, 2010/03/16
- Re: safer way to use gnulib, John W. Eaton, 2010/03/16
- Re: safer way to use gnulib (for other MacOS X users), Ben Abbott, 2010/03/16
- Re: safer way to use gnulib (for other MacOS X users), Thomas Treichl, 2010/03/17
- Re: safer way to use gnulib (for other MacOS X users), John Swensen, 2010/03/17
- Re: safer way to use gnulib (for other MacOS X users), Ben Abbott, 2010/03/17
- Re: safer way to use gnulib (for other MacOS X users), Thomas Treichl, 2010/03/17
- Re: safer way to use gnulib (for other MacOS X users),
Ben Abbott <=
- Re: safer way to use gnulib (for other MacOS X users), Thomas Treichl, 2010/03/18
- Re: safer way to use gnulib, Michael Goffioul, 2010/03/20
- Re: safer way to use gnulib, John W. Eaton, 2010/03/20
- Re: safer way to use gnulib, Michael Goffioul, 2010/03/20
- Re: safer way to use gnulib, John W. Eaton, 2010/03/20
- Re: safer way to use gnulib, Michael Goffioul, 2010/03/20
- Re: safer way to use gnulib, Michael Goffioul, 2010/03/20
- Re: safer way to use gnulib, John W. Eaton, 2010/03/22
- Re: safer way to use gnulib, John W. Eaton, 2010/03/23
- Re: safer way to use gnulib, John W. Eaton, 2010/03/28