octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #61905] Build fails when using slibtool instea


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #61905] Build fails when using slibtool instead of GNU libtool
Date: Wed, 16 Mar 2022 13:21:32 -0400 (EDT)

Update of bug #61905 (project octave):

                  Status:               Need Info => Ready For Test         
                 Release:                   6.4.0 => dev                    
        Operating System:               GNU/Linux => Any                    

    _______________________________________________________

Follow-up Comment #29:

>From the documentation of slibtool:
https://github.com/midipix-project/slibtool
>- `.la wrappers` are always generated, but by default are never installed;
>  `.la wrappers` contain key information that is provided to libtool when
>  generating a shared library or static archive, and which is needed when
>  passing the archive or library as an input argument in .la form to the
>  compiler driver in subsequent link steps. Since `slibtool` is entirely
>  independent of the above wrappers with respect to its own functionality,
>  and given its announced goal to remain compatible with the script-based
>  libtool as much as possible, `slibtool`'s behavior is to always produce
>  `.la wrappers` on the one hand, yet fully ignore their content on the
>  other.

So, .la files are still produced and are compatible with `libtool`. (If they
are not, that is probably a bug in `slibtool`.)
The major difference is that .la files aren't installed by `slibtool`.
We probably shouldn't rely on those files being installed anyway.

I pushed the following change that parses the .la file in the build tree
instead:
https://hg.savannah.gnu.org/hgweb/octave/rev/2d394460429f

That should allow building Octave with `slibtool` while maintaining
compatibility with all platforms that we currently support.

Marking as ready for test.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61905>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]