Re: gcc-4.3 compatibility and cygwin-1.7 policy questions [Was:: Re: SECURITY vulnerabilities update 2007-Sep-25]

Charles Wilson wrote: > Err...but that's a good description of cygwin-1.7, as well. Nobody (as > far as I am aware) is suggesting that a test/preview gcc-4.3 package > should be used as a "regular" compiler for cygwin-1.5. I thought so as well, but people are already putting stuff built with gcc4

Re: gcc-4.3 compatibility and cygwin-1.7 policy questions [Was:: Re: SECURITY vulnerabilities update 2007-Sep-25]

Brian Dessent wrote: > Yes, this is why having an unversioned but shared libgcc in the distro > is such a poison. With the current state of gcc4 it's impossible to win > as maintainer of a C++ library: if you use the default options you get > static libgcc which means your library can't throw or

Re: gcc-4.3 compatibility and cygwin-1.7 policy questions [Was:: Re: SECURITY vulnerabilities update 2007-Sep-25]

Charles Wilson wrote: > Well, if we continue -- at present -- with static libstdc++, then would > we need to continue -- at present -- with static libgcc even for C > libraries? For example: > > cygncurses-N.dll : if this C library is compiled using -shared-libgcc > > then > > cygncurses++-N.d

Re: gcc-4.3 compatibility and cygwin-1.7 policy questions [Was:: Re: SECURITY vulnerabilities update 2007-Sep-25]

Brian Dessent wrote: > Charles Wilson wrote: > >> Or is all the worry about about unwinding a C++ only issue? (And of > > As far as I can tell, it is. Okay, thanks. > Note that gcc doesn't[1] emit any unwind tables for C language input, > even on platforms like Linux that have been DW2 for a lo

Re: gcc-4.3 compatibility and cygwin-1.7 policy questions [Was:: Re: SECURITY vulnerabilities update 2007-Sep-25]

Charles Wilson wrote: > Or is all the worry about about unwinding a C++ only issue? (And of As far as I can tell, it is. Note that gcc doesn't[1] emit any unwind tables for C language input, even on platforms like Linux that have been DW2 for a long time. So if you somehow managed to get yourse

gcc-4.3 compatibility and cygwin-1.7 policy questions [Was:: Re: SECURITY vulnerabilities update 2007-Sep-25]

Yaakov (Cygwin Ports) wrote: > Charles Wilson wrote: >> 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?) > > I'm not sure how much this is all-or-nothing for C, but I imagine that > it w

Re: SECURITY vulnerabilities update 2007-Sep-25

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Charles Wilson wrote: > 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?) I'm not sure how much this is all-or-nothing for C, but I imagine

Re: SECURITY vulnerabilities update 2007-Sep-25

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

Re: SECURITY vulnerabilities update 2007-Sep-25

2008/10/27 Corinna Vinschen: > On Oct 27 11:46, Yaakov (Cygwin Ports) wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Corinna Vinschen wrote: >> >> ORPAHNED: apache2 >> >> Reini Urban: clamav clamav is already updated to 0.94-1 as far as I remember. >> >> Charles Wilson: tiff,

Re: SECURITY vulnerabilities update 2007-Sep-25

On Oct 27 11:46, Yaakov (Cygwin Ports) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Corinna Vinschen wrote: > >> ORPAHNED: apache2 > >> Lapo Luchini: lighttpd > >> Reini Urban: clamav > >> Charles Wilson: tiff, unzip > > > > any news here? > > lighttpd was updated on 20 October

Re: SECURITY vulnerabilities update 2007-Sep-25

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: >> ORPAHNED: apache2 >> Lapo Luchini: lighttpd >> Reini Urban: clamav >> Charles Wilson: tiff, unzip > > any news here? lighttpd was updated on 20 October. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin

Re: SECURITY vulnerabilities update 2007-Sep-25

Hi guys, On Sep 25 23:28, Yaakov (Cygwin Ports) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Unfortunately we haven't made any progress since my last update two > weeks ago, and now there's a new vulnerability (clamav). > > > By maintainer > = > > ORPAHNED: apache

Re: SECURITY vulnerabilities update 2007-Sep-25

2008/9/26 Yaakov (Cygwin Ports): > Unfortunately we haven't made any progress since my last update two > weeks ago, and now there's a new vulnerability (clamav). I'm still working on this in my spare time. 1st problem: configure:16877: result: bugged configure:16886: WARNING: ** bzip2 librari

SECURITY vulnerabilities update 2007-Sep-25

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Unfortunately we haven't made any progress since my last update two weeks ago, and now there's a new vulnerability (clamav). By maintainer = ORPAHNED: apache2 Lapo Luchini: lighttpd Reini Urban: clamav Charles Wilson: tiff, unzip By p