Re: mkoctfile urgently needs attention before Octave 3.6.0 release

[Jordi Gutiérrez Hermoso]

2011/12/29 Lukas Reichlin <address@hidden>:
> On 29.12.2011, at 20:50, Jordi Gutiérrez Hermoso wrote:
>
>> 2011/12/29 Lukas Reichlin <address@hidden>:

>>> I meant that it should work with only one call to mkoctfile. Something like
>>>
>>>    mkoctfile foo.cc --link-to-blas --link-to-lapack
>>
>> Why does this make a difference? Would you prefer if instead the
>> variables were printed by octave-config instead of mkoctfile? What's
>> the problem with calling mkoctfile twice?
>>
>> - Jordi G. H.
>
> This way (mkoctfile foo.cc --link-to-blas --link-to-lapack)
> mkoctfile can deal with conflicts. We just tell mkoctfile to link to
> some of its libraries without giving the platform-specific names
> like -framework Accelerate stored in a variable.

This isn't a real problem.

It seems to me that he real problem is that mkoctfile isn't passing
the -framework argument to the linker and compiler.

See the other thread.

- Jordi G. H.