10862 – `emerge -V` fails with newer versions of gcc ebuilds

Bug 10862 - `emerge -V` fails with newer versions of gcc ebuilds

Summary: `emerge -V` fails with newer versions of gcc ebuilds

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Nicholas Jones (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-11-17 04:11 UTC by SpanKY
Modified:	2011-10-30 22:17 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SpanKY gentoo-dev

2002-11-17 04:11:00 UTC

root@vapier root # emerge -V 
Portage 2.0.44 (default-x86-1.4, gcc-sh: line 1: /usr/bin/gcc: No such file or directory, 
glibc-2.3.1-r2) 
root@vapier root # ls /usr/bin/gcc 
ls: /usr/bin/gcc: No such file or directory 
root@vapier root # gcc-config --get-bin-path 
/usr/i686-pc-linux-gnu/gcc-bin/3.2 
 
so you might want to try using gcc-config, or just planning on the fact that gcc is in 
$PATH somewhere and running `gcc` will get the desired results

Comment 1 SpanKY gentoo-dev

2002-12-16 20:56:14 UTC

http://bugs.gentoo.org/show_bug.cgi?id=12246#c8 <- your answer

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2002-12-18 02:05:31 UTC

fixed in cvs