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

[Michael Orlitzky]

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

[comment #15 comment #15:]
> However, the import libraries are installed to $(DESTDIR)$(octlibdir). So,
the command from comment #14 would probably be a no-op.
> There are a couple of other files installed to $(DESTDIR)$(octlibdir) that
we need to keep.

I see, thanks.

Does "dll.a" appear in any of the autoconf mumbo jumbo on that platform (like
how "dll" appears as acl_shlibext)? If we have that information, my next
choice would be to delete those files specifically from within $(octlibdir).

Otherwise, if there's no collateral damage, I could rm ${f_so}.*, to catch the
".a" at the end.

Finally, if neither of those will work... we're going to wind up hard-coding
something. Either libtool internals, or the alternate names of libraries to
delete. Since the extra libraries are harmless, it wouldn't be too ugly to
delete them based on the dll.a extension. This would still be my last resort
though. (The problem with slibtool is that there is no installed la file to
parse.)

    _______________________________________________________

Reply to this item at:

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

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