Mon 24 Jan 2011 12:15:32 PM UTC, comment #4:
"every mkoctfile command" means mkoctfile commands in the makefile_* [1] (all except makefile_helpers and makefile_all). In revision 8055, I removed the flags and added them again in revision 8063. See [2] for an example. This example is the failing test from comment #2. TG01JD.f is the SLICOT routine which won't pass the test provided by its authors.
Today, Jarno Rajahalme posted on the maintainer list:
Ben and I exchanged a few mails about README.MacOS and I have tried to configure octave-devel with
in a first attempt and added stuff like
and had exactly the config failures that Jarno describes.
My octave_config_info.config_opts for successful 3.3.90 builds are
but with these builds I need to add the mac-specific flags to mkoctfile calls like [2] which is exactly what I want to avoid.
Best Regards,
Lukas
[1]
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/devel/
[2]
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/devel/makefile_minreal.m?r1=8055&r2=8063
|
Mon 24 Jan 2011 04:26:43 AM UTC, comment #3:
I don't see the funny output with 3.3.90 on my Debian system.
I do see the failed test, but I'm not sure how to debug that problem.
What are BLAS_LIBS and LAPACK_LIBS set to in mkoctfile on your system?
When you say
precisely what do you mean by "every mkoctfile command"?
Is your copy of Octave 3.2.4 linked with some different version of the BLAS and LAPACK, or does the mkoctfile script use a different command to compile files? If so, what are the differences?
Also, since I am seeing the test failure, even if it is somehow solved by using Apple's veclib, it would be helpful if we could find out why the test is failing without veclib, so that we can fix the problem for other systems too.
|
Sun 23 Jan 2011 10:11:26 PM UTC, comment #2:
The problem turned out to be not completely solved on my machines, therefore I reopen this bug report.
Octave 3.3.55 and 3.3.90 are able to build my oct-files from control-2.0 without the Mac-specific compiler flags
(MacPorts, Mac OS X 10.6.6, control/devel/makefile_all)
However, some tests are failing, for example the one for SLICOT Fortran routine TG01JD which requires BLAS and LAPACK:
If I add the options
to every mkoctfile command, all tests from test_control pass without problems.
BTW: Note the blanks before octave:2 and the missing output between octave:3 and octave:4. This problem doesn't exist in Octave 3.2.4.
|
Wed 29 Dec 2010 09:51:30 PM UTC, original submission:
Octave 3.3.52 (The most recent "octave-devel +gcc44" version available from MacPorts) running on Mac OS X 10.6.5 (A Core2Duo laptop and a Core i3 desktop) has problems to compile OCT-files that are using LAPACK routines:
When adding the Mac-specific options
"-Wl,-framework" "-Wl,vecLib"
to the mkoctfile arguments like in [1], the problem is solved on my machine. But since these options are Mac-specific, other platforms are broken. Therefore some kind of patch for mkoctfile is needed.
BTW: The problem does not exist when using Octave 3.2.4 from MacPorts.
Steps to reproduce the problem:
- Download the latest SVN version of the control package from [2]
- Install the package by "pkg install" on a Mac with Octave 3.3
- If installation doesn't fail, you can try to run
test_control
at least two times consecutively. All tests should pass.
Best Regards
Lukas
[1]
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/devel/makefile_zero.m
[2]
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/control/?view=tar
|