[Solved] Re: debuilding gcc-3.3 and doxygen

2004-02-29 Thread csj
On 28. February 2004 at 11:30AM +0100,
"J.H.M. Dassen (Ray)" <[EMAIL PROTECTED]> wrote:

> On Thu, Feb 26, 2004 at 21:02:41 +0800, csj wrote:
> > I see a doxygen *++-related bug, but so far the version of
> > doxygen in unstable is still the same as the one in testing.
> 
> Around the time you wrote this, there was a new version of
> doxygen uploaded by the gcc maintainer as a non-maintainer
> upload; that version (1.3.6.20040222-0.1) is now in unstable;
> its changelog includes "Fixing termination problems in 1.3.5
> and 1.3.6 (closes: #232598)."

Ya, that fixed it.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: debuilding gcc-3.3 and doxygen

2004-02-28 Thread J.H.M. Dassen (Ray)
On Thu, Feb 26, 2004 at 21:02:41 +0800, csj wrote:
> I see a doxygen *++-related bug, but so far the version of doxygen in
> unstable is still the same as the one in testing.

Around the time you wrote this, there was a new version of doxygen uploaded
by the gcc maintainer as a non-maintainer upload; that version
(1.3.6.20040222-0.1) is now in unstable; its changelog includes
"Fixing termination problems in 1.3.5 and 1.3.6 (closes: #232598)."

Ray
-- 
"The software `wizard' is the single greatest obstacle to computer literacy
since the Mac."
http://www.osopinion.com/Opinions/MichaelKellen/MichaelKellen1.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



debuilding gcc-3.3 and doxygen

2004-02-26 Thread csj
Am I the only one who can't build gcc-3.3 (3.3.3ds5-1)?  The
build appears to succeed until the point where the documentation
is being built.

Tail of gcc-3.3_3.3.3ds5-1_i386.build:

To avoid this warning please update your configuration file using "doxygen -u"
Warning: Tag `EXT_DOC_PATHS' at line 1074 of file 
/xb/build/debuild/newbuild/gcc-3.3-3.3.3ds5/build/i486-linux/libstdc++-v3/docs/doxygen/user.cfg
 has become obsolete.
To avoid this warning please update your configuration file using "doxygen -u"

From then there's hours of high CPU activity until I abort the
build.  I see a doxygen *++-related bug, but so far the version of
doxygen in unstable is still the same as the one in testing.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]