Summary: | dev-util/kbuild-0.1.4 emerge fails with error "gcc: argument to '-o' is missing" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wai Ling <simotsa> |
Component: | [OLD] Development | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amackenz-gentoo, daniel.glaser, jesse, l_faillie, swapon, v_2e |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Wai Ling
2009-01-18 11:56:45 UTC
It looks like bugzilla have internal error that prevent me for creating attachment. So I am pasting the last few lines from the emerge. ... Making all in doc make[3]: Entering directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed/doc' Updating /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/version.texi restore=: && backupdir=".am$$" && \ am__cwd=`pwd` && cd /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc && \ rm -rf $backupdir && mkdir $backupdir && \ if (/bin/sh /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/config/missing --run makeinfo --version) >/dev/null 2>&1; then \ for f in /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.info /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.info-[0-9] /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.info-[0-9][0-9] /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.i[0-9] /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.i[0-9][0-9]; do \ if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ done; \ else :; fi && \ cd "$am__cwd"; \ if /bin/sh /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/config/missing --run makeinfo -I /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc \ -o /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.info /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.texi; \ then \ rc=0; \ cd /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc; \ else \ rc=$?; \ cd /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc && \ $restore $backupdir/* `echo ".//var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.info" | sed 's|[^/]*$||'`; \ fi; \ rm -rf $backupdir; exit $rc /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/config/help2man --name "stream editor for filtering and transforming text" \ -p sed --include /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.x ../sed/sed > /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/doc/sed.1 make[3]: Leaving directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed/doc' Making all in testsuite make[3]: Entering directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed/testsuite' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed/testsuite' make[3]: Entering directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed' make[2]: Leaving directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed' make[1]: Leaving directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed' cp -f /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed/sed/sed /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/kmk/kmk_sed cp -f /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/kmk/config.h /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/kmk/config.h.linux cp -f /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/sed/config.h /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/sed/config.h.linux /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/kmk/kmk -C /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4 kmk: Entering directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4' kBuild: Pass - Build Programs kBuild: Pass - Libraries kBuild: Compiling kDep - /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/lib/kDep.c gcc: argument to '-o' is missing kmk: *** [/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/obj/kDep/kDep.o] Error 1 The failing command: @gcc -c -O2 -g -O3 -I/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/lib -DKBUILD_VERSION_MAJOR=0 -DKBUILD_VERSION_MINOR=1 -DKBUILD_VERSION_PATCH=4 -DKBUILD_OS_LINUX -DKBUILD_ARCH_X86 -Wp,-MD,/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/obj/kDep/kDep.o.dep -Wp,-MT,/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/obj/kDep/kDep.o -Wp,-MP -o /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/obj/kDep/kDep.o /var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/src/lib/kDep.c kmk: Leaving directory `/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4' make: *** [/var/tmp/portage/dev-util/kbuild-0.1.4/work/kBuild-0.1.4/out/linux.x86/release/bootstrap/ts-stage2-build] Error 2 kBuild/env.sh: info: rc=2: make -f bootstrap.gmk * * ERROR: dev-util/kbuild-0.1.4 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2525: Called die * The specific snippet of code: * kBuild/env.sh --full make -f bootstrap.gmk || die "bootstrap failed" * The die message: * bootstrap failed * * 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/dev-util/kbuild-0.1.4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/kbuild-0.1.4/temp/environment'. Hello, I experienced the same problem and I was also using distcc and ccache. When I removed distcc and cache from FEATURES in /etc/make.conf, emerge -av1 kbuild succeeded. Martin Volf Thanks. It works after I disabled ccache and distcc. Sadly this app is known to it to hickup sometimes with ccache/distcc, though there are cases where it works fine. Can't do something useful here This is still happening. Force disable of FEATURES -distcc -ccache in the ebuild. dev-util/kbuild-0.1.5-r1 same error, same cause (distcc alone in my case). When meerged with 'FEATURES="-distcc" emerge -1v kbuild', it compiles and installs. I have the same problem with VBox client companions, and seems it's related to kbuild. Bye Laurent *** Bug 272391 has been marked as a duplicate of this bug. *** *** Bug 415329 has been marked as a duplicate of this bug. *** Does this still happen with the snapshots in the Portage tree? I tested dev-util/kbuild-0.1.9998_pre20131130 on two different machines. On my 64-bit laptop with gcc-4.9.0_alpha20140423 on which I do not use distcc, the only problem I had was undefined references errors with LTO enabled. It built fine once I disabled LTO. On my 32-bit desktop with gcc-4.9.0_alpha20140416 on which I do use distcc, I went ahead and disabled LTO. The compilation failed, although it was with a different error than the title of this bug. Aside from the march parameter, the CFLAGS/CXXFLAGS and LDFLAGS were the same on both machines. The only significant difference was the use of distcc on the machine where kbuild failed. I checked the kbuild trunk, and it was updated as recently as 6 weeks ago, so I don't know if this has been addressed upstream by now, but this really may just be a conflict between kbuild and distcc. It just happened to me on a fresh install. Disabling distcc made kbuild build without issue. dev-util/kbuild-0.1.9998_pre20131130 I just encountered this bug with the latest stable version 0.1.9998_pre20131130-r1. Why was distcc not forcefully disabled for the ebuild? The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d1b515c88db3255d192e5d469f90405eb2bd33b9 commit d1b515c88db3255d192e5d469f90405eb2bd33b9 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2019-04-20 13:51:09 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2019-04-20 13:51:09 +0000 dev-util/kbuild: Don't build with distcc Closes: https://bugs.gentoo.org/255371 Package-Manager: Portage-2.3.64, Repoman-2.3.12 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> dev-util/kbuild/kbuild-0.1.9998.3149.ebuild | 7 ++++++- dev-util/kbuild/kbuild-9999.ebuild | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) |