bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: multiple definition of `gl_locale_name_thread'


From: Sisyphus
Subject: Re: multiple definition of `gl_locale_name_thread'
Date: Sun, 23 May 2010 17:43:24 +1000


----- Original Message ----- From: "Bruno Haible" <address@hidden>
To: "Sisyphus" <address@hidden>
Cc: <address@hidden>
Sent: Sunday, May 23, 2010 9:42 AM
Subject: Re: multiple definition of `gl_locale_name_thread'


Hi Rob,

No problem building gettext-0.18 with --enable-shared, once I had built a
shared libiconv.

Cool! Very nice. I'll mention how to build for mingw-w64 in the README.woe32,
with the options that you listed.


Those options apply only when using one of the "Automated builds" (cross-compiler). For anyone using one of sezero's "Personal builds" (also available from the same webpage), the configure command is much simpler. All that is probably needed is something like (untested):

./configure --disable-static --enable-shared --build=x86_64-w64-mingw32 
--host=x86_64-w64-mingw32

/usr/local/lib and /usr/local/include are probably found by default, in which case there would be no need for the LDFLAGS and CPPFLAGS args I provided. (They probably weren't needed in my case, either .... I just specify them out of habit bacause, on occasion, I've found it necessary to specify them in the past.)

And, with sezero's builds, the gcc executable is called 'gcc.exe', the ar executable is called 'ar.exe', etc. - as per usual. So they all get found automatically.

Cheers,
Rob



reply via email to

[Prev in Thread] Current Thread [Next in Thread]