----Message d'origine----
De: lenorehor...@sbcglobal.net
Date: 26.08.2009 14:01
À: "MacPorts Users"<macports-users@lists.macosforge.org>
Objet: error compiling Octave
There's a bug report on this, but nothing's happening on it, so I
thought I'd ask the list.
This is the error - before this a lot of things scroll by going fine.
lo-specfun.cc: In function 'Complex xlgamma(const Complex&)':
lo-specfun.cc:327: error: 'lgamma_r' was not declared in this scope
make[2]: *** [lo-specfun.o] Error 1
make[1]: *** [liboctave] Error 2
make: *** [all] Error 2
I contacted the octave people because this looked like they had a
messed up code, but they say it must be the port because some people
are successful compiling on Mac (including the guy who responded to
me). I haven't a clue how the port file could be messed up to cause
the compiler to think a variable hadn't been declared.
I've gotten the same error with Xcode 3.1.2 and Xcode 3.1.3. Maybe
it's a ppc vs intel thing.
Anyone have any clues?
Lenore
From: "nicos.pav...@bluewin.ch" <nicos.pav...@bluewin.ch>
Date: August 26, 2009 7:50:38 AM CDT
To: <lenorehor...@sbcglobal.net>
Subject: RE: error compiling Octave
Reply-To: nicos.pav...@bluewin.ch
Hello,
In the case of Intel (10.5.8, XCode 3.1.3), it is clearly a compiler
problem, where the -arch flag is not understood
by the gcc 4.3 compiler.
I could successfully compile the Octave port with the variant
"octave +g95".
Regards,
Nicolas
Are there any side-effect of using the +g95 variant?
Is there a way to fix the problem with the -arch flag or have the
default compiler not be gcc4.3?
Lenore
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
