This is the mail archive of the cygwin mailing list for the Cygwin 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]

Re: Failed linking gettext-0.18

On 8/6/2010 4:20 AM, Markus Moeller wrote:
Can you tell me what the error means and what I can do to fix it ?

Thank you

"Charles Wilson" <> wrote in message

PCYMTNQREAIYR -----^^^^^^^^^^^^

And please don't top-post:
A: Yes.
> Q: Are you sure?
>>A: Because it reverses the logical flow of conversation.
>>>Q: Why is top posting frowned upon?

It's complicated. The upstream maintainer of gettext REALLY dislikes a mechanism used for symbol resolution by the GNU toolchain (gcc/ld) with DLLs on mingw and cygwin: "auto-import". So, he arranges that gettext is always compiled with --disable-auto-import.

However, recent versions of g++'s runtime library, libstdc++, ITSELF, require auto-import when linking IIUC. Hence, boom.

I'm not sure this is easily fixed. IF I am correct, there are two options: (1) teach g++ how to build a libstdc++ DLL that exports symbols "properly" rather than requiring auto-import. This depends on a new cygwin g++ compiler I think. OR, (2) override the build procedure for gettext to ensure that --enable-auto-import is provided on every link command, AFTER the "default" gettext setting of --disable-auto-import.

IIRC, just setting LDFLAGS before configuring won't do it, because Bruno *deliberately* arranged things to make overriding his desired auto-import behavior difficult.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]