Bug 173963

Summary:	Emerging gcc should not be done with --nodeps
Product:	Gentoo/Alt	Reporter:	Rabbe Fogelholm <rabbe>
Component:	Prefix Support	Assignee:	Gentoo non-Linux Team <alt>
Status:	VERIFIED LATER
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Other
URL:	http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml
Whiteboard:
Package list:		Runtime testing required:	---

Description Rabbe Fogelholm 2007-04-09 22:01:15 UTC

This report refers to the February 4, 2007 version of the document pointed to by the URL.

Step 1.8 says to do `emerge --oneshot --nodeps sys-devel/gcc'. That step may fail with a diagnostic saying that `ld' does not understand the -liconv option, or something like that (sorry, forgot to make notes).

I checked what would happen if --nodeps is omitted. The emerge command will then pull in a few dependencies, one of them being libiconv. Perhaps this fixes the problem with the -liconv option.

I gave it a shot, and it seems to work. After doing `source $EPREFIX/etc/profile', which extends the PATH and some other environment variable values, I now have a working gcc-4.1.2 in the $EPREFIX tree.

Reproducible: Didn't try

Steps to Reproduce:

Comment 1 Fabian Groffen gentoo-dev

2007-07-22 13:12:45 UTC

I cannot reproduce this currently.

Comment 2 Fabian Groffen gentoo-dev

2008-01-26 10:38:25 UTC

can't reproduce it.  Reopen if you can.

Comment 3 Rabbe Fogelholm 2008-01-28 07:26:50 UTC

Hmm .. currently the webpage for prefix portage on Linux does not include any explicit "emerge gcc" step. Probably this report is no longer applicable to the bootstrapping procedure of recent days.