Michael Goffioul wrote:
On Fri, May 2, 2008 at 5:15 AM, Tatsuro MATSUOKA <[EMAIL PROTECTED]> wrote:
Hello
In my octave building for cygwin, non-standard gcc was used.
So I use
export CC='/opt/octave/gcc-3.4.4dw2/bin/gcc'
export CXX='/opt/octave/gcc-3.4.4dw2/bin/g++'
export F77='/opt/octave/gcc-3.4.4dw2/bin/g77'
for octave building.
This infomation is included to the mkoctfile.
The octave-forge packages so far use the complier infomation taken from the
mkoctfile script
or use mkoctfle itself to complipe.
I strongly request the ann package to take similar way at selecting the
complier.
I also had to make a bunch of changes in the build
system to compile the ann package. Its build system is
very Linux-centric.
Unfortunately, even after successfully compiling it, it
crashes after the first ann call (ANNkd_tree). I don't
really have the time to debug it, so I'm afraid I'll left it
out of the Windows binary package.
Since we're complaining about the ann package, I have attached the patch
that was necessary to get it to compile and link with gcc 4.3 in Fedora
9. There were several header declarations missing, and the linker failed
if the binaries were not compiled with the -fPIC flag. This is just a
hack--the best solution would be for the ANN Makefiles to respect the
flags that are set by the configure command as Tatsuro suggested.
Quentin
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
