This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, I built Binutils 2.27 natively on MS-Windows, using mingw.org's MinGW tools, and found that the programs are linked statically to libintl and libiconv, which makes the binaries significantly more fat. Binutils 2.26, built on the same machine, was linked dynamically to those libraries. Digging a little deeper, I see that intl/config.intl says in Binutils 2.27: USE_NLS='yes' LIBINTL='d:/usr/lib/libintl.a d:/usr/lib/libiconv.a' LIBINTL_DEP='' INCINTL='' whereas in 2.26 it said this: USE_NLS='yes' LIBINTL='-lintl' LIBINTL_DEP='' INCINTL='' The same 'configure' command was used in both cases. Can someone tell what am I doing wrong, and how can I cause the build to use the dynamic link to shared libraries? Is it a bug that I should report to the Binutils Bugzilla? TIA P.S. I'm not subscribed to this list, so please CC me on the responses.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |