[RFC] ready for cygport to default to gcc4?
Dave Korn
dave.korn.cygwin@googlemail.com
Fri Apr 3 23:38:00 GMT 2009
Corinna Vinschen wrote:
> On Apr 3 11:30, Charles Wilson wrote:
>> If I rebuild gettext using gcc4 AND if the switch to gcc4 + shared
>> libgcc means that there is some sort of breakage (e.g. between a client
>> that uses the old, static runtime, and this DLL that uses the new,
>> dynamic runtime) -- then EVERY package that relies on libintl8 just
>> broke.
>
> I'm not sure there is really such a interdependency. Shouldn't the
> static libgcc3 functions and the new shared gcc4 libgcc functions
> co-exist and not notice each other?
Can't throw and catch exceptions between the two types of code.
> I understand that there is trouble along the way, but, actually, do we
> really have a choice? As you write in your other mail, we're in a
> transition period. We're transitioning in at least two ways, a very
> new Cygwin and a very new gcc. We will have to drag it along and
> we can't force other maintainers to do a JIT job. At the very least,
> if some packages break, the maintainer will probably notice (or be
> noticed) and provide a new package within a couple of days.
I was wondering what percentage of the repository is sufficiently
g-b-s-tastic or cygport-ified to be able to more-or-less automatedly rebuild.
cheers,
DaveK
More information about the Cygwin-apps
mailing list