Jules Colding wrote:
This could be a shot in the dark, but I think that you should remerge
your autoconf and automake packages to see if that affects this.
I'll be doing that.
OK, I get a segfault doing that:
############## snip ###############
test -z "/usr/share/automake-1.9/Automake" || mkdir -p --
"/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/Automake"
/bin/install -c -m 644 'Config.pm'
'/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/Automake/Config.pm'
make[4]: Leaving directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/Automake'
make[3]: Leaving directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/Automake'
make[2]: Leaving directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/Automake'
Making install in am
make[2]: Entering directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am'
make[3]: Entering directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am'
make[3]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/automake-1.9/am" || mkdir -p --
"/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/am"
/bin/sh: line 1: 16093 Segmentation fault mkdir -p --
"/var/tmp/portage/automake-1.9.5/image//usr/share/automake-1.9/am"
make[3]: *** [install-dist_amDATA] Error 139
make[3]: Leaving directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib/am'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/automake-1.9.5/work/automake-1.9.5/lib'
make: *** [install-recursive] Error 1
!!! ERROR: sys-devel/automake-1.9.5 failed.
!!! Function src_install, Line 36, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.
############## snip ###############
Wouldn't it be a good idea on this point to reemerge coreutils or maybe
the whole of "system"?
Is the correct way doing:
emerge -e system
emerge -e system
emerge -e world
emerge -e world
Well, since world includes system, if you want to rebuild *everything*,
I would think the following should be sufficient
emerge --oneshot gcc binutils
(check gcc-config and binutils-config to ensure sanity)
emerge -e world
The above should ensure that everything gets rebuilt with the rebuilt
version of gcc and binutils.
To save some time, you could try just system instead of world. That
*should* still give you a sane build environment, but if you get many
more segfaults, I am going to start thinking that you have some hardware
problems...
-Richard
--
gentoo-user@gentoo.org mailing list
