| 1 |
With the stabilization of the nptl-only glibc-2.4, many users are |
| 2 |
finding out that they installed their systems with |
| 3 |
CHOST=i386-pc-linux-gnu, and now need to either mask the new glibc, or |
| 4 |
figure out how to change their CHOST. |
| 5 |
|
| 6 |
I am not able to find any official guide on changing CHOST, and the |
| 7 |
information on the wiki and forums is, well, "confusing" at best. |
| 8 |
|
| 9 |
What I've basically been telling people is to: |
| 10 |
|
| 11 |
1. update chost |
| 12 |
2. run /usr/portage/scripts/bootstrap.sh |
| 13 |
3. emerge -e system |
| 14 |
4. emerge -e world |
| 15 |
|
| 16 |
But I don't have any great confidence that these instructions will |
| 17 |
work, and that someone won't end up needing to boot from their live CD |
| 18 |
to fix or re-install their systems, as I've never had to change CHOST |
| 19 |
myself. |
| 20 |
|
| 21 |
http://article.gmane.org/gmane.linux.gentoo.user/169894 |
| 22 |
|
| 23 |
So I really want to know what the official position is on CHOST |
| 24 |
changes, and whether the above instructions are reasonable. Obviously |
| 25 |
I'm looking specifically at i386->i686, and not i*86->x86_64. |
| 26 |
|
| 27 |
If we could get something in to GWN on this, that would be great. |
| 28 |
|
| 29 |
-Richard |
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives