[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #42002] pkg/mkoctfile need to support '-framew

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #42002] pkg/mkoctfile need to support '-framework' flags; patch supplied
Date: Mon, 31 Mar 2014 19:25:16 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20100101 Firefox/17.0

Follow-up Comment #6, bug #42002 (project octave):

Thanks for the detailed explanation, that does clear things up for me.
Especially the package example that fails.

Ok, let me rephrase a little bit what I said: mkoctfile should be able to
produce oct-files that work with Octave without the user needing to specify
indirect dependencies. Whether that means all deps are linked in implicitly
(link-all-deps) or not, however it's done under the hood. But you've shown
that's not the case here.

I'm guessing that odepkg is using some BLAS functions directly and so that's
why it needs to link with BLAS itself, which makes perfect sense. The
communications package does the same thing with HDF5_LIBS. I agree that this
is a valid use case and should be addressed somehow.

On a related note, I see that -framework and -Wl,-framework are used
inconsistently in Octave's configure.ac, m4/acinclude.m4, and m4/ax_blas.m4.

You seem to prefer -framework to -Wl,-framework, and as you said GNU libtool
supports it, so maybe you should also make a patch and make a case for
consistency in the Octave build as well, so all frameworks are linked in using
the same syntax, and then the case for mkoctfile to support whichever way
Octave's build considers "official" becomes easier. Right now it's half and
half, so it's easy to say "don't use -framework".


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]