Summary: | aclocal is killed with SIGILL while emerging sys-devel/libtool-2.2.6b | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kevin Haddock <kevinhaddock> |
Component: | [OLD] Development | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | erik |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | relevant files |
Description
Kevin Haddock
2009-12-13 20:37:03 UTC
Created attachment 212917 [details]
relevant files
Given that aclocal is a script, your system is definitely messed up… CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer -mmmx -msse -msse2 -msse3 -mfpmath=sse" given this line I wonder if your P4 does support SSE3 or not; you're using -march=native so all the -m$simd are either pointless or forcing something your system doesn't support. I'd say INVALID. Same here: * Running autoheader ... [ ok ] * Running automake --add-missing --copy ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-devel/libtool-2.2.6b/temp/automake-24870.out * ERROR: sys-devel/libtool-2.2.6b failed: * Failed Running automake ! * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 6887: Called eautoreconf * environment, line 4720: Called eautomake * environment, line 4693: Called autotools_run_tool 'automake' '--add-missing' '--copy' * environment, line 4193: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of 'emerge --info =sys-devel/libtool-2.2.6b', * the complete build log and the output of 'emerge -pqv =sys-devel/libtool-2.2.6b'. * The complete build log is located at '/var/tmp/portage/sys-devel/libtool-2.2.6b/temp/build. log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-2.2.6b/temp/e nvironment'. * S: '/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b' >>> Failed to emerge sys-devel/libtool-2.2.6b, Log file: >>> '/var/tmp/portage/sys-devel/libtool-2.2.6b/temp/build.log' * Messages for package sys-devel/libtool-2.2.6b: * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-devel/libtool-2.2.6b/temp/automake-24870.out * ERROR: sys-devel/libtool-2.2.6b failed: * Failed Running automake ! * * Call stack: * ebuild.sh, line 54: Called src_unpack * environment, line 6887: Called eautoreconf * environment, line 4720: Called eautomake * environment, line 4693: Called autotools_run_tool 'automake' '--add-missing' '--copy' * environment, line 4193: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of 'emerge --info =sys-devel/libtool-2.2.6b', * the complete build log and the output of 'emerge -pqv =sys-devel/libtool-2.2.6b'. * The complete build log is located at '/var/tmp/portage/sys-devel/libtool-2.2.6b/temp/build. log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-2.2.6b/temp/e nvironment'. * S: '/var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b' And if you don't provide emerge --info, you're not going to get any help. This seems to have been the fault atleast for me. ***** automake ***** ***** PWD: /var/tmp/portage/sys-devel/libtool-2.2.6b/work/libtool-2.2.6b ***** automake --add-missing --copy configure.ac:125: require Automake 1.10.1, but have 1.10 |