Opened 13 years ago

Closed 12 years ago

#42 closed defect (wontfix)

lapack.a vs lapack.so

Reported by: fmargot Owned by: andreasw
Priority: minor Component: configuration tests
Version: 0.5 Keywords:
Cc: fmargot@…

Description

I configure on Fedora 5 with

enable_shared=no enable_static=yes

I have both liblapack.a and liblapack.so in /usr/lib. I would like to link with liblapack.a, but the configure script selects liblapack.so. How do I force it to use liblapack.a?

Change History (2)

comment:1 Changed 12 years ago by andreasw

  • Status changed from new to assigned

Sorry, it seems that noone replied to this ticket...

The flags you specify don't influence what libraries libtool is looking for, only which types of libraries are generated (in your specific project).

You can try the following:

Specify the complete path to the library file (such as --with-lapack=/usr/lib/liblapack.a). This might do it, but sometimes libtool changes the linker flags (very annoying).

Otherwise, I think there is also a flag, something like -static for libtool or the compiler, which prompts it to generate an executable that does not depend on shared libraries. You could put that into ADD_CXXFLAGS or so...?

comment:2 Changed 12 years ago by andreasw

  • Resolution set to wontfix
  • Status changed from assigned to closed

No reply in a while. Closing ticket.

Note: See TracTickets for help on using tickets.