Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 206913 - media-gfx/yafray ebuild uses $MAKEOPTS which may have incompatible values
Summary: media-gfx/yafray ebuild uses $MAKEOPTS which may have incompatible values
Status: RESOLVED DUPLICATE of bug 202547
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 206914 (view as bug list)
Depends on:
Blocks: 337831
  Show dependency tree
 
Reported: 2008-01-21 19:31 UTC by Peter Gantner (a.k.a. nephros)
Modified: 2010-09-18 10:04 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Gantner (a.k.a. nephros) 2008-01-21 19:31:17 UTC
Hi!

I am using the following in make.conf:
 MAKEOPTS="-j3 -s -l 2.5"

With GNU make, -l controls (not) spawning new make processes after high load.
For scons, -l deals with library paths, and will not acccept integer or float parameters, resulting in:

>>> Source unpacked.
>>> Compiling source in /tmp/portage/media-gfx/yafray-0.0.9-r1/work/yafray ...
usage: scons [OPTION] [TARGET] ...

SCons error: option -l: invalid integer value: '2.7'

and the usual emerge bailout.

The ebuild has in src_compile:
    scons ${MAKEOPTS} prefix="/usr"
which causes this error.

Reproducible: Always



Expected Results:  
The ebuild should not assume that MAKEOPTS only contains -jN values as the user may have set other valid make options.
MAKEOPTS should probably be parsed to use just -jN for scons.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2008-01-21 19:34:25 UTC
As noted on the other bug - if you have a generic solution to scons suckage, feel free to suggest it... Thanks.

*** This bug has been marked as a duplicate of bug 202547 ***
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2008-01-21 19:43:27 UTC
*** Bug 206914 has been marked as a duplicate of this bug. ***