Bug#304659: Fix is now in upstream CVS
This bug has now been fixed in CVS upstream. However until it is fixed in Debian (sarge specifically) gcc-3.4 is technically FTBFS in sarge. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#304659: Fix is now in upstream CVS
On Tue, Apr 19, 2005 at 09:30:00AM -0400, Len Sorensen said > This bug has now been fixed in CVS upstream. However until it is fixed > in Debian (sarge specifically) gcc-3.4 is technically FTBFS in sarge. So this is a gcc problem, not a bazaar one? -rob -- Words of the day: colonel Telex AMW Yukon counter terrorism New World Order -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#304659: Fix is now in upstream CVS
On Wed, Apr 20, 2005 at 06:34:49PM +1000, Rob Weir said > On Tue, Apr 19, 2005 at 09:30:00AM -0400, Len Sorensen said > > This bug has now been fixed in CVS upstream. However until it is fixed > > in Debian (sarge specifically) gcc-3.4 is technically FTBFS in sarge. > > So this is a gcc problem, not a bazaar one? Oops, wrong bug. -rob -- Words of the day:mania Exon Shell JFK AMEMB Montenegro beanpole Europol -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#304659: Fix is now in upstream CVS
On Wed, Apr 20, 2005 at 06:34:49PM +1000, Rob Weir wrote: > On Tue, Apr 19, 2005 at 09:30:00AM -0400, Len Sorensen said > > This bug has now been fixed in CVS upstream. However until it is fixed > > in Debian (sarge specifically) gcc-3.4 is technically FTBFS in sarge. > > So this is a gcc problem, not a bazaar one? It is a bug in doxygen 1.4.2 which is now fixed in doxygen CVS. doxygen should never segfault on any input, and it did. If doxygen 1.4.2 stays in sarge as is however, it technically qualifies as making gcc-3.4 FTBFS which I guess would be a problem for gcc-3.4 although not at all their fault. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
