On 9/9/06, Boyd Stephen Smith Jr. <[EMAIL PROTECTED]> wrote:
On Saturday 09 September 2006 15:50, "Mark Knecht" <[EMAIL PROTECTED]>
wrote about '[gentoo-amd64] gcc-4.1.1 update - emerge -eav world
necessary?':
> Hi,
> Looking at the gcc update instructions I wondered if the last
> emerge -eav world step is actually necessary for correct system
> operation?
IIRC, both the emerge -e steps were added because some users reported
problems.
In that case I would go ahead and do it......IF......
I actually finished the first emerge -eav system. My gcc upgrade
failed. Apparently there has been some bug reports with the same
problems many months ago but no resolution. I don't know why it imacts
me. I don't have any cross-development stuff on my machine, although
reading a bit it appears that the AMD64 tool chain has some built in.
Anyway, here's the bug report showing where I'm stopped. I'm not clear
if my machine is even usable at this point. sandbox won't emerge.
emerge system failed in the middle.
http://bugs.gentoo.org/show_bug.cgi?id=133209
Bummer.
Could this have anything to do with a chroot environment being on the
system? There is an init script that mounts all ofthat stuff
automatically. Is there some confusion about the tool set in there?
lightning ~ # ls -la /etc/init.d/gentoo32
-rwxr-xr-x 1 root root 1842 Dec 7 2005 /etc/init.d/gentoo32
lightning ~ #
> I'm satisfied if the system gets rebuilt over the next few weeks with
> normal updates. However that would leave some apps and other things
> built on the old compiler. This method would have everything built
> with the new one, but is it necessary for correct/stable operation?
Feel free to skip them, but if your system acts wonky -- particularly C++
programs -- please perform them before filing a bug report.
More than fair, assuming I ever get that far! :-(
Thanks!
- Mark
--
[email protected] mailing list
