On Fri, 9 Sep 2005, Dave Nebinger wrote:
/bin/sh
/var/tmp/portage/gcc-3.3.6/work/gcc-3.3.6/libstdc++-v3/docs/doxygen/run_doxygen
\
--mode=man ${srcdir} ${builddir})
: : NOTE that this may take some time...
/usr/bin/doxygen
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
Well, doesn't the above note explain it all? Personnally I'm not using
doxygen so I had no problems with the gcc upgrade...
I hadn't the faintest idea about what doxygen is. It must have been
emerged as a dependency for something.
When you say system hangs, you don't say if it's hanging for minutes,
hours, whatever. But since it's running against a config file in
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3, I'd be
willing to bet that it will take a great deal of time to complete.
Emerge (not the system) just hangs. I didn't wait time enough...I'm
assuming this has to do with the doc USE variable. Actually, I
upgraded doxygen (which compiled with no optimizations) and gcc now
compiles. Still, couldn't compile mozilla, even with -doc.
Something is still very much wrong.
Perhaps you need to remove something from your USE flags to keep doxygen from
running during the gcc build, or try giving it enough time to complete.
Thanks for the reply.
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
