[Octave-bug-tracker] [bug #61905] Build fails when using slibtool instead of GNU libtool

[Michael Orlitzky]

Follow-up Comment #5, bug #61905 (project octave):

[comment #3 comment #3:]
> I don't remember what the default for `--enable-no-undefined` was in the
past. But that might have been fixed in the meantime(?).
> Afaict currently on the stable branch (will become Octave 7), the configure
script only sets the corresponding linker flags to something non-empty by
default for msdosmsvc, mingw*, AIX, BeOS, or OS/2. Are you building for one of
those hosts?

No, I could be wrong about that part. Out of the box, Octave failed to build
with slibtool due to undefined symbols, and adding
--enable-link-all-dependencies fixed it. At that point I savoured my temporary
victory and failed to check the other flag combinations. So maybe it crashes
regardless of --enable-no-undefined.


> I can't comment on the sed replacement in the .la files.
> I don't know anything about slibtool or how it differs from GNU libtool.
Could you please elaborate why that doesn't work for you, or how this should
be done differently so it would work for both tools?

Why what doesn't work for me? There's probably a more portable alternative,
but I'd need to know what problem the sed is intended to fix first, i.e. what
goes wrong if you skip it and just make the automake "make install" do its
thing?


    _______________________________________________________

Reply to this item at:

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

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