James Ferguson wrote:
gcc-config error: Could not run/locate "i386-pc-linux-gnu-gcc"
make[2]: *** [vncauth.o] Error 1
make[2]: Leaving directory
`/var/tmp/portage/tightvnc-1.3_alpha5/work/vnc_unixsrc/libvncauth'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/var/tmp/portage/tightvnc-1.3_alpha5/work/vnc_unixsrc'
make: *** [World] Error 2
If anyone could suggest a cause for this i would be greatfull, as a
lot of other software i have been trying to install has been failing
to compile and im starting to think it could all be related.
Generally, this is caused by changing your CHOST [That's when it
happened to me.], but I suppose it could just been some portage/ebuild
oddity. IIRC, this can be corrected with an emerge -e system.
As a workaround, when you find a package that gives this error, go into
the portage work directory and sed -e 's/i386-/i686-/g' all the auto*
generated files (particularly the Makefile) [Heck, you might be able to
safely do this to ALL the files.], then move through the ebuild manually
(see 'man ebuild').
This should cause the system to look for i686-pc-linux-gnu-gcc, which
you should have.
--
Boyd Stephen Smith Jr.
[EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list
