Re: [gentoo-user] Can't compile gcc
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
Re: [gentoo-user] Can't compile gcc
/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...
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.
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.
--
gentoo-user@gentoo.org mailing list
[gentoo-user] Can't compile gcc
Title says (almost) all.
Trying to upgrade gcc-3.3.5.20050130-r1 to gcc-3.3.6
Emerge hangs and I have to kill it with Ctrl-C:
creating libg2c.la
(cd .libs && rm -f libg2c.la && ln -s ../libg2c.la libg2c.la)
make[3]: Leaving directory
`/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libf2c'
: make ; exec true CC='/var/tmp/portage/gcc-3.3.6/work/build/gcc/xgcc
-B/var/tmp/portage/gcc-3.3.6/work/build/gcc/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include'
LD='/usr/i686-pc-linux-gnu/bin/ld' LIBTOOL='/bin/sh ./libtool' WARN_CFLAGS='-W -Wall'
CFLAGS='-O2 ' CPPFLAGS='' DESTDIR='' AR='ar' RANLIB='ranlib' prefix='/usr'
exec_prefix='/usr' libdir='/usr/lib' libsubdir='/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6'
tooldir='/usr/i686-pc-linux-gnu' multi-do DO="all-unilib"
make[2]: Leaving directory
`/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libf2c'
make[1]: Leaving directory `/var/tmp/portage/gcc-3.3.6/work/build'
(srcdir=`cd /var/tmp/portage/gcc-3.3.6/work/gcc-3.3.6/libstdc++-v3;
${PWDCMD-pwd}`; \
builddir=`${PWDCMD-pwd}`; \
/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
Warning: Tag `CGI_NAME' at line 1045 of file
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
has become obsolete.
To avoid this warning please update your configuration file using "doxygen
-u"
Warning: Tag `CGI_URL' at line 1051 of file
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
has become obsolete.
To avoid this warning please update your configuration file using "doxygen
-u"
Warning: Tag `DOC_URL' at line 1057 of file
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
has become obsolete.
To avoid this warning please update your configuration file using "doxygen
-u"
Warning: Tag `DOC_ABSPATH' at line 1063 of file
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
has become obsolete.
To avoid this warning please update your configuration file using "doxygen
-u"
Warning: Tag `BIN_ABSPATH' at line 1068 of file
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
has become obsolete.
To avoid this warning please update your configuration file using "doxygen
-u"
Warning: Tag `EXT_DOC_PATHS' at line 1074 of file
/var/tmp/portage/gcc-3.3.6/work/build/i686-pc-linux-gnu/libstdc++-v3/docs/doxygen/man.cfg
has become obsolete.
To avoid this warning please update your configuration file using "doxygen
-u"
I tried with CFLAGS="" and still nothing. The system has been giving
some trouble, that's why I thought the problem might be with gcc, having
run out of ideas (e.g., to compile lshw I had to remove '-pipe' from
CFLAGS).
I also tried removing /var/tmp/portage/gcc*
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
