This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: SECURITY vulnerabilities update 2007-Sep-25
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: Mailing List: CygWin-Apps <cygwin-apps at cygwin dot com>
- Date: Mon, 27 Oct 2008 21:42:12 -0400
- Subject: Re: SECURITY vulnerabilities update 2007-Sep-25
- References: <48DC650B.7040407@users.sourceforge.net> <20081027091918.GA28578@calimero.vinschen.de>
Corinna Vinschen wrote:
>> ORPAHNED: apache2
>> Lapo Luchini: lighttpd
>> Reini Urban: clamav
>> Charles Wilson: tiff, unzip
I'm a-gettin' there. autotools first, then everything else.
Related, but maybe a new topic:
BTW, what's the consensus on cygwin-1.7 wrt gcc? I know there is not
supposed to be -- absent runtime support library and exception unwinding
issues -- any ABI breakage between gcc-3.4.5 and gcc-4.x in C.
But.
Our gcc-4.x could use a different runtime support library (e.g. shared
libgcc if desired. Do we?).
gcc-4.x also changed to dwarf2 (I think? right?) exception unwinding,
which means that libgcc is a little different even when static.
So...should cygwin-1.7 packages all be built using gcc-4.x, or not? (And
is it really, as I fear, an all-or-nothing proposition given the libgcc
changes?)
--
Chuck