On Tue, Jun 05, 2012 at 08:07:42AM -0700, Alexander Hansen wrote: > On 6/5/12 7:11 AM, Jordi Gutiérrez Hermoso wrote: > > ... > > You're trying to pass compiler flags to mkoctfile. It doesn't accept > > compiler flags. It accepts a very small subset of flags that look like > > compiler flags, but the weird flags that McOS10 uses aren't accepted > > (why -framework Accelerate instead of -lAccelerate)? > > > > frameworks are directories, and contain headers as well as libraries. > Using -framework gives you the -I as well as the -l.
So that's the point --- I didn't see this. So Octave was probably installed as supposed to be. But mkoctfile simply notes the flags used in building Octave. This poses a problem, we rely on the linker flags returned by mkoctfile -p ... and pass them to mkoctfile in some packages. But this will not work under these circumstances. What is to be done here? Can Octaves buildsystem be made to use -l (and -h) instead of -framework even on MAC? Or ar we obliged to check and transform strings returned by 'mkoctfile -p ...' in each package where it is needed (if we do not want supply each such package with a configure script, which would be even more effort)? Olaf -- public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
