Re: [OctDev] bug with optim-1.1.0.tar.gz and mac os 10.7.4

[Olaf Till]

On Wed, Jun 06, 2012 at 12:50:53PM -0400, John W. Eaton wrote:
> On  6-Jun-2012, Olaf Till wrote:
> 
> | On Wed, Jun 06, 2012 at 11:45:02AM -0400, John W. Eaton wrote:
> | > On  6-Jun-2012, Alexander Hansen wrote:
> | > 
> | > | What ultimately gets done is up to you folks, of course.
> | > | 
> | > | As a near-term workaround, might I suggest putting something in the
> | > | online documentation telling OS X users to avoid later mkoctfile usage
> | > | problems by always using the "-Wl,-framework,foo" syntax rather than
> | > | just "-framework foo" when using frameworks?  This would apply for
> | > | configuring the Octave build as well as when they build tools that use
> | > | Octave.
> | > | 
> | > | That way they have a better chance of being able to hand-build Octave
> | > | and use "pkg install -forge <pkgname>" if they don't want to use a
> | > | package manager.
> | > | -- 
> | > | Alexander Hansen, Ph.D.
> | > | Fink User Liaison
> | > | http://finkakh.wordpress.com/2012/02/21/got-job/
> | > 
> | > Another possibility is to pass options that are not recognized by
> | > mkoctfile using the environment variables CPPFLAGS (for the C
> | > preprocessor) CFLAGS (for the C compiler) FFLAGS (for the Fortran
> | > compiler) CXXFLAGS (for the C++ compiler) and LDFLAGS (for the
> | > linker).
> | > 
> | > jwe
> | 
> | Which should solve the original problem. I'll make this change to the
> | optim package and suggest it for the other affected packages.
> 
> One thing to be careful about is whether to preserve the values of
> these variables from the environment and to avoid wiping out the
> default values of things like CXXFLAGS and CFLAGS (-O2 -g) and FFLAGS
> (-O).
> 
> jwe

Ok, thanks. Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc
Description: Digital signature