[lto-plugin, build] Don't link libiberty.a into liblto-plugin.a
Dave Korn
dave.korn.cygwin@gmail.com
Wed Dec 15 20:16:00 GMT 2010
On 15/12/2010 18:46, Ralf Wildenhues wrote:
> You can influence that at configure time (AC_DISABLE_{STATIC,SHARED} or
> LT_INIT options disable-{static,shared}), as well as in the Makefile
> ({AM,libfoo_la}_LDFLAGS += -static or
> {AM,libfoo_la}_LIBTOOLFLAGS = --tag=disable-{static,shared}).
> For fixing the original issue reported by Rainer in
> http://gcc.gnu.org/ml/gcc-patches/2010-12/msg01116.html
> using --tag=disable-static as above ought to be the easiest workaround
> (untested) until libtool is fixed to not add a .a file to a .a file.
Yeah, I prefer the tag too, because the AC_DISABLE_xxx and LT_INIT(xxx)
solutions get overridden if someone explicitly configures with --enable-static
at the top-level. Testing this instead of the previous one:
lto-plugin/ChangeLog:
* Makefile.am (AM_LIBTOOLFLAGS): Define.
* Makefile.in: Regenerate.
cheers,
DaveK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lto-static-take2.diff
Type: text/x-c
Size: 418 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20101215/1932588c/attachment.bin>
More information about the Gcc-patches
mailing list