Lapack compilation flags

[Sylvestre Ledru]

On 14/11/2012 08:59, Victor Liu wrote:
> On 11/13/2012 11:37 PM, Sylvestre Ledru wrote:
>> Hello,
>>

> Basically, there are two ways to fix the bug: specify compiler flags, or
> modify the codebase to use avoid using huge local arrays. I am
> advocating for the former here since it appears the latter solution
> would require an API change.
> 
> The fix I described in my previous message would be a change that you
> would implement in the makefile (more precisely, make.inc), which I
> would think is at the package maintainer's discretion. I imagine that
> the devs would prefer not to include compiler specific build flags in
> their default make.inc.
They could.

> The compilation flag method would completely fix the problem for the
> official Debian libraries, but still leave it open for other platforms.
> This could potentially be confusing if people find that their
> multithreaded code works on a Debian based distribution, but then breaks
> when they transition to another platform, which is a much more common
> thing to do in scientific computing.
It is why it should be included in the upstream Make.inc.

> I would be happy to open a bug report, but I am unsure of which package
> I should file it under (liblapack-dev, liblapack3, liblapack3gf?). All
> these different package names are very confusing to me.
liblapack3 will be fine.

Thanks,
Sylvestre