Pulling the switch on GCC4.

Corinna Vinschen corinna-cygwin@cygwin.com
Tue Sep 29 07:02:00 GMT 2009

On Sep 29 03:20, Dave Korn wrote:
> Corinna Vinschen wrote:
> > Does the new gcc version now set the TSAWARE flag by default?  That
> > would be quite important, so that at leats new applications run on a
> > Terminal Server right from the start.  Especially bash is an important
> > candidate.
>   Arrgh.  No, it doesn't.  Blast, knew I was bound to forget something.  We'll
> need to hang on to peflags for now, but I'll certainly add the relevant option
> to the linker spec for next time round.  (We should probably send a patch to
> that effect upstream as well.)
>   Do you want to delay the release for this?  It will take about a fortnight
> to do a respin.  I was planning to start a new spin rolling in the background
> basically as soon as I've uploaded this version (just to add the missing patch
> for pr38579), so 4.3.4-2 could follow equally as quickly as it would take me
> to respin 4.3.4-1 and fix both these issues in the same timescale without
> delaying the initial rollout, if you think that's ok.

If 4.3.4-2 comes really, *really* soon, then it's ok.  It's about time
to get this flag set by default for Cygwin packages.  As I said, it's
especially important for bash and coreutils which are the most called
tools during postinstall.  It doesn't look overly reassuring if the
postinstalls crash and you can't even start bash from the Cygwin
shortcut on the machine.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-apps mailing list