This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [lto-plugin, build] Don't link libiberty.a into liblto-plugin.a
On 15/12/2010 17:06, Rainer Orth wrote:
> Hi Dave,
>
>>> I can do that, but I still can't see any use for a static plugin
>>> anywhere (not knowing Windows at all, fortunately :-)
>> It's not a windows thing, it's just that libtool always builds both a static
>> and a shared library. There is in fact a potential use for it; libtool
>
> I know, but you can disable that at configure time. I don't know how to
> make that the default for lto-plugin, but suppose it is doable.
AC_DISABLE_STATIC, or pass "disable-static" as an argument to LT_INIT,
according to the manual. I'll try the attached (on top of reverting your
patch); perhaps you'd like to try with your debug-build assembler and check
that it also avoids the assert for you.
lto-plugin/ChangeLog:
* configure.ac (AM_PROG_LIBTOOL): Replace deprecated name ...
(LT_INIT): ... with new version, and disable building static library.
cheers,
DaveK
Index: configure.ac
===================================================================
--- configure.ac (revision 167858)
+++ configure.ac (working copy)
@@ -6,7 +6,7 @@ AM_INIT_AUTOMAKE([foreign no-dist])
AM_MAINTAINER_MODE
AC_PROG_CC
AC_SYS_LARGEFILE
-AM_PROG_LIBTOOL
+LT_INIT([disable-static])
ACX_LT_HOST_FLAGS
AC_SUBST(target_noncanonical)
AC_TYPE_INT64_T