Re: libtool 2.2.2 fails to create shared object

[Bruno Haible]

Ralf Wildenhues wrote:
> I would not call that a regression.  libtool never defined -shared
> to do anything, but now it does,

But this sentence in the doc

   "In general, each MODE-ARG is interpreted by programs libtool invokes,
    rather than libtool itself."

means that an option '-shared' passed to libtool was always supported in
the sense that it was passed to the underlying compiler.

> it never allowed the use of several
> source files on one command line (although it probably should), and it
> never documented that compiling and linking could be merged.

So what's the documented way to create a shared library for LD_PRELOAD,
independently of the --enable/--disable-shared flags passed by the user?
I now have to use a separate subdirectory with a separate configure file
just for this purpose. It would be nice if there was an easier way to
achieve this.

> If you look closely, libtool 1.5.x doesn't change anything on your
> command line, not even -fPIC -DPIC; and it won't translate those flags,
> or -shared FWIW, to the flags needed on other systems: you can just omit
>   /bin/sh ../libtool --mode=link
>
> from it and have the same results and portability issues.

Oh well. Could this be documented, please? I'd like to know in advance
in which situations there is no point fighting against libtool's command
line processing - when libtool does not provide any service!

Bruno