Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 173963 - Emerging gcc should not be done with --nodeps
Summary: Emerging gcc should not be done with --nodeps
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: x86 Other
: High normal (vote)
Assignee: Gentoo non-Linux Team
Depends on:
Reported: 2007-04-09 22:01 UTC by Rabbe Fogelholm
Modified: 2008-01-28 07:26 UTC (History)
0 users

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


Note You need to log in before you can comment on or make changes to this bug.
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.