Both have similar error. Already remerged libtool, ran revdep-rebuild even tried emerge -e sys-apps/attr. Currently have 2.4.38 installed, can't even rebuild that. checking whether ln -s works... yes checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext checking for rpm... /usr/bin/rpm ./configure: line 20471: test: too many arguments checking for an ANSI C-conforming const... yes checking for mode_t... yes checking for working alloca.h... yes checking for alloca... yes configure: creating ./config.status config.status: creating include/builddefs config.status: creating include/config.h include/builddefs:58: *** missing separator. Stop. * * ERROR: sys-apps/attr-2.4.41 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2492: Called die * The specific snippet of code: * emake || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/attr-2.4.41/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/attr-2.4.41/temp/environment'. * * Messages for package sys-apps/attr-2.4.41: * * ERROR: sys-apps/attr-2.4.41 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2492: Called die * The specific snippet of code: * emake || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/attr-2.4.41/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/attr-2.4.41/temp/environment'. Reproducible: Always
Created attachment 147230 [details] emerge --info
Err sorry, 2.4.38 isn't in portage, can't emerge 2.4.39 either.
line 58 is an empty line so getting an error there is a little odd please post the file in question as an attachment and post `emerge --verbose --info` as well
Created attachment 147298 [details] emerge --info --verbose
Created attachment 147299 [details] include/builddefs
Looking at the section where it goes wrong, it appears to have to do with rpm. I don't have rpm installed. There is a /usr/bin/rpm however, but it's just a symlink to /bin/true. flaptoppy attr-2.4.41 # whereis rpm rpm: /usr/bin/rpm flaptoppy attr-2.4.41 # readlink /usr/bin/rpm /bin/true
Renamed /usr/bin/rpm, all is fine. Wonder where /usr/bin/rpm came from.
My bad, probably created the rpm link for the Juniper SSL-VPN appliance we have. It works fine under linux, but it gives errors about rpm missing. Linking /usr/bin/rpm to /bin/true solves the issue. Nasty fix. Sorry to have bugged you with this.
looks like the sgi packages rely on the rpm version format ... if you give it something else, it falls apart: RPM_VERSION = 6 Inc <http://gnu it law Meyering
*** Bug 219679 has been marked as a duplicate of this bug. ***
*** Bug 233134 has been marked as a duplicate of this bug. ***