--with-blas/lapack being ignored

[John W. Eaton]

On  5-Dec-2007, Ben Abbott wrote:

| 
| On Dec 5, 2007, at 11:52 AM, John W. Eaton wrote:
| 
| > On  5-Dec-2007, Ben Abbott wrote:
| >
| > | Running fntests still crashes.
| > |
| > | [...]
| > |    src/octave/scripts/time/datestr.m ...................... PASS    
| > 32/32
| > |    src/octave/scripts/time/datevec.m ......................panic:  
| > Bus
| > | error -- stopping myself...
| > | Bus error
| > |
| > | Which may be duplicated with the simpler ....
| > |
| > | strptime ('09/13', '%m/%d')
| > | panic: Bus error -- stopping myself...
| > | attempting to save variables to `octave-core'...
| > | save to `octave-core' complete
| > | Bus error
| >
| > OK, so what happens if you run Octave with gdb and execute the
| > strptime command above?  Precisely where is it crashing?
| >
| > jwe
| 
| I haven't (yet) tried compiling with the debug info in place. However,  
| this is what I get
| 
| Reading symbols for shared libraries . done
| octave:1> strptime ('09/13', '%m/%d')
| Reading symbols for shared libraries . done
| 
| Program received signal EXC_BAD_ACCESS, Could not access memory.
| Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
| 0x9110f590 in strlen ()
| (gdb)

At this point, type "where" at the gdb prompt to get a stack trace.
Of course, it would also be more useful to see what values are
present, but for that you'll need to use -g when compiling at least
the C++ parts of Octave.

jwe