Re: [RFC] ready for cygport to default to gcc4?

[Dave Korn <dave dot korn dot cygwin at googlemail dot com>]

Corinna Vinschen wrote:
> On Apr  3 08:44, Dave Korn wrote:
>>   Hmm, I feel a third option coming on.
>>
>>   I could do a special case hack, that works just for libstdc++, by putting
>> the objects for the overrideable functions into the import library archive
>> instead of the DLL.  But then we'd still have problems if a library built as a
>> DLL overrides operator new (that bit will work), and then the application does
>> so too; we'll just have moved the interposing problem 'out one layer' from
>> libstdc++ to the client dll.  Not sure if I like that either.
>>
>>   I think I'd better just pull a bunch of all nighters and get this weak
>> symbol support working ASAP :-)
> 
> Btw., did the pe-coff flags option already make it into binutils?  We
> should make sure that newly built applications (including Cygwin's utils
> itself) have the TS-aware bit set by default.

  Yeh, it did.  Once the weak symbols fix is working and there's a new
binutils package, I'll extend the gcc linker spec to add the right option.

    cheers,
      DaveK