#11635: Ensure that libraries link to the shared version of NTL by default
----------------------------------------------------------+-----------------
       Reporter:  kcrisman                                |         Owner:  tbd 
        
           Type:  defect                                  |        Status:  
needs_review
       Priority:  minor                                   |     Milestone:  
sage-5.4    
      Component:  cygwin                                  |    Resolution:      
        
       Keywords:  cygwin ntl libtool spkg                 |   Work issues:      
        
Report Upstream:  N/A                                     |     Reviewers:      
        
        Authors:  Karl-Dieter Crisman, Jean-Pierre Flori  |     Merged in:      
        
   Dependencies:                                          |      Stopgaps:      
        
----------------------------------------------------------+-----------------
Description changed by jdemeyer:

Old description:

> In #11547, we added copying of several needed dlls on Cygwin.  However,
> in the meantime NTL had a fairly major update (#5731).
>
> From version 5.5, NTL provides a new build system using libtool (although
> libtool itself is not provided!) to generate shared libraries.
> On Cygwin, libtool properly install the shared library as cygntl-?.dll in
> the bin directory and the import file as libntl.dll.a in the lib
> directory, together with a libtool file libntl.la and a static version of
> the library as libntl.a.
>
> In particular, this ensures that the shared version is linked with by
> default because ld/gcc/g++ find the .dll.a file in the lib directory
> (which points to the dll file in the bin directory) before the .a file.
>
> Moreover, only moving the previously built libntl.dll to libntl.dll.a was
> not a solution.
> Indeed, the built file hardcoded its own build-time name into itself (as
> a DT_SONAME on linux), so that libraries linked to it (before or after
> renaming, does not matter) would in fact search for a file with the build
> time name... and fail.
>
> The spkg available at
> http://perso.telecom-paristech.fr/~flori/sage/ntl-5.5.2.p0.spkg
> vastly simplifies the old spkg-install, uses the (slightly patched)
> upstream build system and includes its own version of libtool (or rather
> the tools needed to generate it on the fly).

New description:

 In #11547, we added copying of several needed dlls on Cygwin.  However, in
 the meantime NTL had a fairly major update (#5731).

 From version 5.5, NTL provides a new build system using libtool (although
 libtool itself is not provided!) to generate shared libraries.
 On Cygwin, libtool properly install the shared library as cygntl-?.dll in
 the bin directory and the import file as libntl.dll.a in the lib
 directory, together with a libtool file libntl.la and a static version of
 the library as libntl.a.

 In particular, this ensures that the shared version is linked with by
 default because ld/gcc/g++ find the .dll.a file in the lib directory
 (which points to the dll file in the bin directory) before the .a file.

 Moreover, only moving the previously built libntl.dll to libntl.dll.a was
 not a solution.
 Indeed, the built file hardcoded its own build-time name into itself (as a
 DT_SONAME on linux), so that libraries linked to it (before or after
 renaming, does not matter) would in fact search for a file with the build
 time name... and fail.

 '''spkg''': http://www.infres.enst.fr/~flori/sage/ntl-5.5.2.p0.spkg

 This spkg vastly simplifies the old spkg-install, uses the (slightly
 patched) upstream build system and includes its own version of libtool (or
 rather the tools needed to generate it on the fly).

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11635#comment:54>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to