92208 – 'emerge --emptytree system' if CHOST was changed

Bug 92208 - 'emerge --emptytree system' if CHOST was changed

Summary: 'emerge --emptytree system' if CHOST was changed

Status:	RESOLVED INVALID

Alias:	None

Product:	[OLD] Docs-user
Classification:	Unclassified
Component:	Handbook (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Docs Team

URL:	http://www.gentoo.org/doc/en/handbook...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-05-10 20:11 UTC by Douglas R. Hoffman
Modified:	2005-05-19 02:50 UTC (History)
CC List:	0 users

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 Douglas R. Hoffman 2005-05-10 20:11:33 UTC

'emerge --emptytree system' needs be performed if CHOST was changed.

Current documention indicates the "--emptytree" emerge should be performed if either CFLAGS or CXXFLAGS was changed.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Jonathan Smith (RETIRED) gentoo-dev

2005-05-11 05:16:56 UTC

the handbook also tells you to only change CHOST if you are doing a stage1 and _really_ know what you are doing. if you do a stage 1, then emerge -e world is unncessary. if you do a stage3, then changing your chost is a bad idea...

Comment 2 Sven Vermeulen (RETIRED) gentoo-dev

2005-05-19 02:50:55 UTC

We do not support changing the CHOST setting for non-stage1 installations.