Re: mkoctfile urgently needs attention before Octave 3.6.0 release

[Lukas Reichlin]

On 29.12.2011, at 14:47, Jordi Gutiérrez Hermoso wrote:

> Don't panic. :-)
> 
> Calm down.

I'll do my very best ;-)

>> In order to circumvent these problems, I propose the following
>> solution that works from both Octave prompt and OS shell: Addition
>> of a new option "--link-all-libs" to mkoctfile
> 
> No, this is not the solution. We need to understand the actual
> problem. You are proposing a heavy-handed solution because you don't
> understand the actual problem, and neither do we. We should work to do
> that instead of trying to revert to an old barbaric method of linking
> that happened to work for your case.
> 
> Marco has already proposed a solution that seems to work for other
> cases. We are only missing yours.
> 
> - Jordi G. H.

I'm glad that Marco sent me a patch. But it's just a workaround for the 
problem, not a solution. It's not good when you have to resort to the shell, 
query some configuration variables and then feeding the result to the next call 
of mkoctfile. It should be possible from the Octave prompt and without tedious 
fiddling with intermediate variables. If a mkoctfile option "--link-all-libs" 
is not acceptable to you, a selective approach to link specific libraries has 
to be considered (e.g. "--link BLAS_LIBS", "--link LAPACK_LIBS", …)

Lukas