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

[John W. Eaton]

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