This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Fix bootstrap with --disable-shared and linker plugin
* Jan Hubicka wrote on Sun, Jan 09, 2011 at 03:02:56PM CET:
> >
> > This kind of subverts the intention of --disable-shared disabling shared
> > library generation. But there is precedent with libiberty; and one can
> > argue both to be internal libraries. I assume there are other mechanisms
> > in place actually disabling lto-plugin on systems where shared libraries
> > are not supported at all?
>
> There is no point building plugin on hosts that do not support shared
> libraries since the plugin can not be plugged into linker.
Sure. The question is whether --enable-lto should override
--disable-shared or vice versa. I agree it is somewhat of a bikeshed
question, but it may be prudent to at least document the intended
semantics.
> Toplevel configure already contains tests whether the plugin makes sense for
> host (enabling it for ELF and cygwin targets only) Is there easy test to see if
> shared libs can be built we can put into toplevel configure?
Well, you can add AC_PROG_LIBTOOL to configure.ac and test
$enable_shared = no afterwards, but that's not what I'd call an "easy
and lightweight test". ;-) I'm also not convinced it's a good idea to
introduce at this point in development.
Cheers,
Ralf