Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 523636 - sys-block/thin-provisioning-tools MAKEOPTS="V=0" - src_compile(): make: 0: Command not found
Summary: sys-block/thin-provisioning-tools MAKEOPTS="V=0" - src_compile(): make: 0: Co...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Robin Johnson
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-24 17:52 UTC by Chandler Paul
Modified: 2014-09-25 18:26 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,6.48 KB, text/plain)
2014-09-24 17:54 UTC, Chandler Paul
Details
emerge --info (emerge_info.txt,5.26 KB, text/plain)
2014-09-24 17:57 UTC, Chandler Paul
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chandler Paul 2014-09-24 17:52:45 UTC
In my /etc/portage/make.conf, I have the line MAKEOPTS="-j12 V=0", the V=0 reducing the verbosity of the ebuilds that I emerge. This works with every ebuild I've tried except for this one. When attempting to emerge sys-block/thin-provisioning-tools-0.3.2-r1 with MAKEOPTS="-j12 V=0", the ebuild fails with the following error:
"make: 0: Command not found"
When trying to emerge it with MAKEOPTS="-j12", the ebuild emerges as-per usual.

Reproducible: Always

Steps to Reproduce:
1. export MAKEOPTS="-j12 V=0"
2. as root, run "emerge thin-provisioning-tools"
Actual Results:  
>>> Compiling source in /tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/work/thin-provisioning-tools-0.3.2 ...
make V=0 
    [CXX] base/base64.cc
0 x86_64-pc-linux-gnu-g++ -c -I. -I. -I./thin-provisioning -O2 -march=native -pipe -g -Wall -fno-strict-aliasing   -o base/base64.o base/base64.cc
make: 0: Command not found
make: *** [base/base64.o] Error 127
 * ERROR: sys-block/thin-provisioning-tools-0.3.2-r1::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-block/thin-provisioning-tools-0.3.2-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-block/thin-provisioning-tools-0.3.2-r1::gentoo'`.
 * The complete build log is located at '/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/temp/environment'.
 * Working directory: '/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/work/thin-provisioning-tools-0.3.2'
 * S: '/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/work/thin-provisioning-tools-0.3.2'

>>> Failed to emerge sys-block/thin-provisioning-tools-0.3.2-r1, Log file:

>>>  '/tmp/portage/sys-block/thin-provisioning-tools-0.3.2-r1/temp/build.log'

Expected Results:  
Emerged normally, without dying
Comment 1 Chandler Paul 2014-09-24 17:54:37 UTC
Created attachment 385410 [details]
build.log
Comment 2 Chandler Paul 2014-09-24 17:57:53 UTC
Created attachment 385412 [details]
emerge --info

This is the output from emerge --info '=sys-block/thin-provisioning-tools-0.3.2-r1::gentoo'
Comment 3 Samuli Suominen (RETIRED) gentoo-dev 2014-09-25 18:26:48 UTC
MAKEOPTS is for setting -jX level as an argument of emake, and it's only for that

MAKEFLAGS is generic GNU make environment variable to pass other flags

Don't mix up MAKEFLAGS and MAKEOPTS