| View previous topic :: View next topic |
| Author |
Message |
escozzia
n00b
Joined: 08 May 2011
Posts: 14
|
 Posted: Sun Aug 07, 2016 12:10 am Post subject: |
 |
|
| NeddySeagoon wrote: | escozzia,
Looks like it. You cannot rely on your toolchain to (re)build itself correctly as it seems to be broken.
Its worth booting into memtest to see what that says about your hardware. |
Hmm I just did a memtest pass without any errors, so the hardware is probably okay.
I guess that means it's a toolchain rebuild for me - do you have any pointers on the best way to do that? Obviously just re-emerging everything won't work, but it seems as though just downloading binaries and replacing the installed ones would be a bit crazy |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54794
Location: 56N 3W
|
| Posted: Sun Aug 07, 2016 10:57 am Post subject: |
|
|
escozzia,
You need a setup as described in fix my Gentoo
Instead of using emerge to generate the required binaries, there is a script.
When you get the the part that reads | Code: | More Packages
emerge whatever you need. You don't need to do it all in one go. /home/rescue will stay around until you delete it and its only a chroot away. When you come back, don't forget the /usr/portage bind mount. |
Do | Code: | | /usr/portage/scripts/bootstrap.sh |
That's actually stage1 of a stage1 install. It builds your toolchain. This script does not support resume.
You can probably install all the binaries you get, into your main system, with emerge -K too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
escozzia
n00b
Joined: 08 May 2011
Posts: 14
|
| Posted: Sun Aug 07, 2016 4:03 pm Post subject: |
|
|
| NeddySeagoon wrote: | escozzia,
You need a setup as described in fix my Gentoo
Instead of using emerge to generate the required binaries, there is a script.
When you get the the part that reads | Code: | More Packages
emerge whatever you need. You don't need to do it all in one go. /home/rescue will stay around until you delete it and its only a chroot away. When you come back, don't forget the /usr/portage bind mount. |
Do | Code: | | /usr/portage/scripts/bootstrap.sh |
That's actually stage1 of a stage1 install. It builds your toolchain. This script does not support resume.
You can probably install all the binaries you get, into your main system, with emerge -K too. |
Hmm, I followed that guide, and then did
| Code: |
emerge '=sys-kernel/gentoo-sources-4.1.15-rc1'
|
inside of the chrooted system, followed by
| Code: |
emerge -K sys-apps/baselayout sys-apps/texinfo sys-devel/binutils sys-devel/gcc sys-devel/gettext sys-libs/glibc sys-libs/zlib virtual/libc sys-devel/bc
source /etc/profile
env-update
|
Inside the parent system, then rebuilt 4.1.12. However, it still doesn't boot.
I did try building the emerged 4.1.15 from inside of the chrooted system, and that one does boot, so it's looking likely that I just didn't emerge the package that's at fault.
I'll just try to
from the child and then install every single binary package into the parent, which might take a while. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54794
Location: 56N 3W
|
| Posted: Sun Aug 07, 2016 5:18 pm Post subject: |
|
|
escozzia,
Your parent world file will be polluted with @system packages.
That | Code: | | emerge -K sys-apps/baselayout sys-apps/texinfo sys-devel/binutils sys-devel/gcc sys-devel/gettext sys-libs/glibc sys-libs/zlib virtual/libc sys-devel/bc |
should have been -K1 or -K --oneshot.
There is an emerge option to remove entries from the world file without uninstalling the package.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
escozzia
n00b
Joined: 08 May 2011
Posts: 14
|
| Posted: Mon Aug 08, 2016 3:16 am Post subject: |
|
|
Hurmm still no good. I did the
in the child, followed by a
just to make sure I got everything, then went back to the parent and did
| Code: |
emerge -K1 $(find /usr/portage/packages/ -type f -name '*.tbz2' | egrep -v 'udev|sandbox' | sed -e 's/.*packages\/\(.*\)-[0-9]\+.*.tbz2/\1/g' | xargs)
|
I rebooted, rebuilt the kernel and still no good. The child kernel still works okay though. I'm stumped - that command reinstalled just about everything I can imagine could be the source (except for udev and sandbox - could it be those? udev was bizarrely giving me a conflict, and reinstalling sandbox caused every build to fail) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
