fntests.m during and after make

[Thomas Treichl]

Ben Abbott schrieb:
>> 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

Yes, Octave.app is a f2c build.

If you run fntest from Octave then you still pass all tests, right? This just 
happens if you call make check after you build your Octave? So what about this one:

   http://www.nabble.com/forum/ViewPost.jtp?post=9048718&framed=y

Please also try the following line and tell us what you see:

   octave-2.9.17:1> strptime ('09/13', '%m/%d')

What I would expect is:

   ans =
   {
     usec = 0
     sec = 0
     min = 0
     hour = 0
     mday =  13
     mon =  8
     year = 0
     wday =  6
     yday =  256
     isdst = 0
     zone =
   }

Thomas