[Octave-bug-tracker] [bug #53627] build: oct files should not need to link with -loctinterp -loctave

[Mike Miller]

Follow-up Comment #22, bug #53627 (project octave):

This is all very confusing and very operating system dependent.

I would think we want to follow the libtool default behavior, at least on as
many operating systems as it is possible to do so. On Windows clearly it is
not, DLLs need to be built against the stub library that contains the
definitions for them to use. But on most other operating systems, it is a
choice, and I think the choice should be to default to allowing undefined
symbols.

Glancing through the libtool code, there is a set of linker flags for allowing
undefined symbols, another set of flags for no undefined symbols, as well as
whether one behavior or the other is unsupported.

On GNU/Linux, I think all of the flags are empty, so the linker is called the
same way with or without the -no-undefined option.

I think on Unix operating systems we should not be using -no-undefined. It
seems to only be required on Windows/MinGW/Cygwin, BeOS, OS/2, and AIX v3.

I think libtool will either error if you try to build for Windows without this
option, or maybe build a static library instead of a shared object and print a
warning.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53627>

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