[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fntests.m during and after make
From: |
Ben Abbott |
Subject: |
Re: fntests.m during and after make |
Date: |
Tue, 04 Dec 2007 08:53:00 -0800 |
On Tuesday, December 04, 2007, at 08:41AM, "Thomas Treichl" <address@hidden>
wrote:
>Ben Abbott schrieb:
>> On Dec 3, 2007, at 10:20 PM, Ben Abbott wrote:
>>> On Dec 3, 2007, at 12:07 PM, John W. Eaton wrote:
>>> I've located a specific failure, but am not sure it is a bug, or a
>>> feature of the way I've build octave.
>>>
>>> "test datevec" produces a kernel panic. After some testing I found
>>> that any date string with either ":" or "/" give that result. Thus,
>>> each of the following ...
>>>
>>> datevec("07-Sep-2000 15:38:09")
>>> datevec("07-Sep-2000")
>>> datevec("09/07/00")
>>> datevec("09/13")
>>> datevec("15:38:09")
>>> datevec("3:38:09 PM")
>>> datevec("15:38")
>>> datevec("03:38 PM")
>>> datevec("03/13/1962")
>>>
>>> ... produce
>>>
>>> ---------------------------------
>>> panic: Bus error -- stopping myself...
>>> attempting to save variables to `octave-core'...
>>> save to `octave-core' complete
>>> Bus error
>>> ---------------------------------
>>>
>>> While the following work as expected
>>>
>>> datevec("07-Sep-2000 15:38:09")
>>> datevec("07-Sep-2000")
>>> all(datenum(datevec([-1e4:1e4]))==[-1e4:1e4]'))
>>> t = linspace (-2e5, 2e5, 10993);
>>> all (abs (datenum (datevec (t)) - t') < 1e-5));
>>>
>>> I've built octave on an intel Mac using Fink's package management. The
>>> config parameters and build script are below
>>>
>>> ---------------------------------
>>> ConfigureParams: F77=%p/bin/g95 --libexecdir='${prefix}/lib'
>>> CompileScript: <<
>>> #!/bin/sh -ev
>>> gcclib=`%p/bin/g95 --print-lib`
>>> FLIBDIR=`dirname $gcclib`
>>> export FLIBS="-L${FLIBDIR} -lf95"
>>> export FFLAGS='-O2'
>>> export CFLAGS='-O2'
>>> export CXXFLAGS='-O2'
>>> ./configure %c
>>> make
>>> make check
>>> ---------------------------------
>>>
>>> I'm hoping someone will point out that I've made an error. If not I'll
>>> file a bug report.
>>>
>>> Ben
>>>
>>
>> oppps, the failures should have been
>>
>> datevec("09/07/00")
>> datevec("09/13")
>> datevec("15:38:09")
>> datevec("3:38:09 PM")
>> datevec("15:38")
>> datevec("03:38 PM")
>> datevec("03/13/1962")
>>
>> Ben
>
>Hi Ben,
>
>sorry but I can't see the problem in Octave.app 2.9.17 running on an IA32 Mac:
>
> octave-2.9.17:1> datevec("09/07/00")
> ans =
> 2000 9 7 0 0 0
> octave-2.9.17:2> datevec("09/13")
> ans =
> 2007 9 13 0 0 0
> octave-2.9.17:3> datevec("15:38:09")
> ans =
> 2007 12 4 15 38 9
> octave-2.9.17:4> datevec("3:38:09 PM")
> ans =
> 2007 12 4 15 38 9
> octave-2.9.17:5> datevec("15:38")
> ans =
> 2007 12 4 15 38 0
> octave-2.9.17:6> datevec("03:38 PM")
> ans =
> 2007 12 4 15 38 0
> octave-2.9.17:7> datevec("03/13/1962")
> ans =
> 1962 3 13 0 0 0
> octave-2.9.17:8> test datevec
> PASSES 11 out of 11 tests
>
>Thomas
>
You're using f2c correct?
Perhaps this is a compiler issue and not related to OS?
Has anyone used g95 on Linux to build Octave?
Ben
- fntests.m during and after make, Ben Abbott, 2007/12/03
- fntests.m during and after make, John W. Eaton, 2007/12/03
- Re: fntests.m during and after make, Ben Abbott, 2007/12/03
- Re: fntests.m during and after make, Ben Abbott, 2007/12/03
- Re: fntests.m during and after make, Thomas Treichl, 2007/12/04
- Re: fntests.m during and after make,
Ben Abbott <=
- Re: fntests.m during and after make, Thomas Treichl, 2007/12/04
- Re: fntests.m during and after make, Marius Schamschula, 2007/12/04
- Re: fntests.m during and after make, John W. Eaton, 2007/12/04