Bug 153849

Summary:	gcc-upgrading: where to look at CHOST settings and irreproducible upgrade behavior
Product:	[OLD] Docs on www.gentoo.org	Reporter:	nicky <vanforeest>
Component:	Other documents	Assignee:	Docs Team <docs-team>
Status:	RESOLVED NEEDINFO
Severity:	enhancement	CC:	amne
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://www.gentoo.org/doc/en/gcc-upgrading.xml
Whiteboard:
Package list:		Runtime testing required:	---

Description nicky 2006-11-02 12:05:14 UTC

Following the advice of Wernfried Haas I post this enhancement.

=== Start email of Wernfried: 

Hi,
On Wed, Nov 01, 2006 at 11:44:46PM +0100, nicky van foreest wrote:
> The point is this. I had gcc-3.4... working, but emerge refused to
> change to gcc-4.1.1. with the command 'emerge -avu gcc'. It was
> necessary to give the command: emerge -avu =gcc-4.1.1'.
> I could not find this in the document.

That is pretty strange, emerge -avu should always install the latest
version available, which ARCH are you on?

> Would you also be so kind to mention that CHOST can be found in
> /etc/make.conf, so that people know what option to pass to gcc-config?

Sounds like a good idea, however i'm not responsible for maintaining
the guide as the docs team takes care of that these days. Could you
either mail Jan (jkt@gentoo.org) or open a bug report about it and
assign it to the docs team?

cheers,
       Wernfried

Comment 1 nm (RETIRED) gentoo-dev

2006-11-02 12:14:42 UTC

Uh, sounds like you're running a very weird, possibly screwed up system, and/or it's just a Portage bug. If you can repeat the behavior, and can provide some good details like emerge --info, maybe we can decide what to do in our docs, but I can tell you that we write the guides to be future proof, so we can't recommend that users upgrade *to a specific version*; our instructions are just to upgrade to the latest with emerge -avu.

Comment 2 Jan Kundrát (RETIRED) gentoo-dev

2006-11-03 10:02:42 UTC

(In reply to comment #0)
> > The point is this. I had gcc-3.4... working, but emerge refused to
> > change to gcc-4.1.1. with the command 'emerge -avu gcc'. It was
> > necessary to give the command: emerge -avu =gcc-4.1.1'.
> > I could not find this in the document.

We won't change that. If it didn't work, it could be because of some bug in Portage or just caused by some configuration weirdness.

> > Would you also be so kind to mention that CHOST can be found in
> > /etc/make.conf, so that people know what option to pass to gcc-config?

Nah, as the CHOST actually doesn't have to be specified in the /etc/make.conf but inherited from the system profile, the only point to point to :) is the output of `emerge --info`.

Not worth it, IMHO.