dc_lapack in generated arch.make (in 4.1-b1)

Bug #1627936 reported by migueldiascosta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Siesta
Status tracked in Trunk
4.1
Fix Released
Low
Nick Papior
Trunk
Fix Released
Low
Nick Papior

Bug Description

According to the Makefile, dc_lapack has been deprecated in favor of libsiestaLAPACK, but in some cases configure still adds it to arch.make (which will now always fail).

In my case, this happens when there is a working external lapack (so libsiestaLAPACK is not added) but for some reason dc_lapack is still added.

Even if there is a valid reason for configure to add a packaged lapack, shouldn't it now always be libsiestaLAPACK instead of dc_lapack?

description: updated
Revision history for this message
Nick Papior (nickpapior) wrote :

Thanks for the bug-report.

Currently the configure script is missing an overhaul. There are several missing library checks and indeed some of the configure output comes out erroneously.

We are aware of the short-comings of the configure script and will currently advice the output as a guideline arch.make.

Changed in siesta:
status: New → Triaged
importance: Undecided → Low
Nick Papior (nickpapior)
Changed in siesta:
status: Triaged → Fix Committed
Revision history for this message
migueldiascosta (migueldiascosta) wrote :

Hi,

saw your changes but it seems to me that configure will still add dc_lapack.a later - the if block starting at line 7360 adds dc_lapack.a in both cases.

Revision history for this message
Nick Papior (nickpapior) wrote :

We have discontinued support for the configure script due to missing updates and dependency checks.

Hence, later revisions have removed configure.

Revision history for this message
migueldiascosta (migueldiascosta) wrote :

fair enough

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.