FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 05-03-2011, 09:32 AM
Charles Plessy
 
Default Mass GCC 4.6 bug filling ( Bug#624997: writerperfect: FTBFS: Style.hxx:36:45: error: 'NULL' was not declared in this scope)

Dear Lucas and everybody,

the recent archive rebuild uncovered a large number of GCC 4.6 build failures
(that could been already forseen from Launchpad). In the long run, I find very
impressive the contribution from the major Linux distribution to their upstreams
for keeping them up to date with recent toolchains.

However, given my experience of repetitive patching cycles with earlier GCC
updates, it would be pointless to spend a lot of energy updating our packages
now if it is only to realise in few weeks that the next GCC update would
require yet another header.

So can we have some perspectives and gross time frame, sent on
debian-devel-announce@l.d.o, that we could also use as a reference when we will
forward the issue to our upstreams ? For the packages I maintain, I would
prefer to see – and help – these bugs fixed by new upstream release rather than
by patch.

Have a nice day,

--
Charles Plessy
Illkirch-Graffenstaden, Alsace, France


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110503093212.GB12232@merveille.plessy.net">http://lists.debian.org/20110503093212.GB12232@merveille.plessy.net
 
Old 05-03-2011, 09:38 AM
Sandro Tosi
 
Default Mass GCC 4.6 bug filling ( Bug#624997: writerperfect: FTBFS: Style.hxx:36:45: error: 'NULL' was not declared in this scope)

On Tue, May 3, 2011 at 11:32, Charles Plessy <plessy@debian.org> wrote:
> However, given my experience of repetitive patching cycles with earlier GCC
> updates, it would be pointless to spend a lot of energy updating our packages
> now if it is only to realise in few weeks that the next GCC update would
> require yet another header.
>
> So can we have some perspectives and gross time frame, sent on
> debian-devel-announce@l.d.o, that we could also use as a reference when we will
> forward the issue to our upstreams ? *For the packages I maintain, I would
> prefer to see – and help – these bugs fixed by new upstream release rather than
> by patch.

Who do you expect to send such communication? the gcc maintainer? good
luck with that.

--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTikTeMvmN4XLJhiqcBP5YGLgSM1kog@mail.gmail.com ">http://lists.debian.org/BANLkTikTeMvmN4XLJhiqcBP5YGLgSM1kog@mail.gmail.com
 

Thread Tools




All times are GMT. The time now is 07:30 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org