I've been trying to set up an HP Omnibook 5700cT with Gentoo over the past three days and keep running into a brick wall when trying to emerge groff. I've set up the hard drive, got the pcmcia network card up and running, and untarred the stage 2 tarball. However, after chrooting into the root partition, performing an 'env-update' and 'emerge system', it continually fails when trying to handle compiling groff, and it doesn't seem to matter what version of groff I choose as I've now tried to explicitly emerge 1.18.1-r3, 1.18.1-r2, 1.18-r3 with the same exact results as shown below (see attached log file for full details). <snip> make[2]: Entering directory `/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/roff/troff' g++ -I. -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/roff/troff -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/include -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/include -DHAVE_CONFIG_H -O3 -mcpu=i586 -funroll-loops -pipe -c env.cc g++ -I. -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/roff/troff -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/include -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/include -DHAVE_CONFIG_H -O3 -mcpu=i586 -funroll-loops -pipe -c node.cc g++ -I. -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/roff/troff -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/include -I/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/include -DHAVE_CONFIG_H -O3 -mcpu=i586 -funroll-loops -pipe -c input.cc g++: Internal error: Terminated (program cc1plus) Please submit a full bug report. See <URL:http://bugs.gentoo.org/> for instructions. {standard input}: Assembler messages: {standard input}:49384: Warning: end of file not at end of a line; newline inserted make[2]: *** [input.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1/src/roff/troff' make[1]: *** [src/roff/troff] Error 2 make[1]: Leaving directory `/var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1' make: *** [all] Error 2 </snip> Please let me know what other information about the system would be helpful for solving this issue, as I'd really like to get the little laptop up and running with the fastest linux distro available.
Created attachment 21974 [details] Full log of emerge session This is the full log of the emerge session gathered via the following command: % emerge groff 2>&1 | tee /tmp/groff-1_18_1_r3.log It doesn't seem to matter which version of groff I use, as the same failure results in all four that I've tried to date. Therefore, I'm submitting the log of the most up-to-date version available in portage.
Oddly enough, I forgot to mention, that oddly enough, I can manually complete the compilation by doing the following: % cd /var/tmp/portage/groff-1.18.1-r3/work/groff-1.18.1-r3 % make Of course, I can't do all of the other things that get done by emerge such as setting up links and what not, but I am able to at least compile it (haven't tried installing, however as I didnt' want to muddy the waters).
ouch, I'm investigating this as well, bobby can someone from the release team please have a look at this as well.
This may or may not be helpful. The laptop won't boot from CDROM, so I've had to use Slackware 8.1 boot/root disks to get to a command prompt. Their 'pcmcia' utility set up the network for me, and I manually added routes and set IP addresses via 'route' and 'ifconfig'. Then I partitioned the hard drive, built file systems, turned on swap and mounted everything appropriately. Everything from that point forward follows the standard gentoo installation instructions.
Are there any workarounds that would allow me to finish the installation without first emerging groff? I know that it's used for man pages and what not, but I'm fuzzy on what else needs it. As things stand, I can live without man pages, so if that's all that groff is needed for, then I would gladly put it aside in order to get on with the rest of the install.
Bobby, try to change your flags from -mcpu=i586 to -march=i586 dunno, it's just a hunch
Seemant, thanks for the tip, and I'll try it tonight when I get home from work. I often confuse the difference between -march and -mcpu anyway, so it could easily be the culprit. Hope that it works. Would you like to see the rest of my make.conf file or any other file on that system?
Bobby, if you could paste the output of `emerge info` that would be good too
Created attachment 22158 [details] output from "emerge info"
Seemant, I swiched from 'mcpu=i586' to '-march=i586' and groff now emerges just fine. Don't understand why it works, but am marking this bug closed.
