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