On 4/15/2011 3:29 AM, Martin J. Evans wrote:
On 15/04/11 00:03, p...@0ne.us wrote:
Slaven Rezic wrote:
Chris Marshall<jns-cmarsh...@comcast.net> writes:
Is there a way to detect parallel make usage
(e.g., gmake -j 3) in a Makefile.PL so that
I can either exit (because it doesn't work and
is not supported) or override (use -j 1 ) so
that the make will work?
Is this a hypothetical problem or are there some testers around using
parallel make? I would expect that many distributions break on parallel
make...
Regards,
Slaven
I remember Florian Ragwitz ( FLORA ) toying around with it and asking on
IRC about general smoking stuff. Not sure if he is actually running a
parallel smoker :)
It's also on my todo list to run a smoker like that someday... *evil grin*
Someone is trying (don't know if they are a smoker) but failing horribly:
http://www.cpantesters.org/cpan/report/cc67d4d8-6bf3-1014-b3c9-804ae2d7fb8e
Output from 'C:\strawberry\c\bin\dmake.EXE -j 3 -j 3':
Usage:
dmake.EXE [-P#] [-{f|K} file] [-{w|W} target ...] [macro[!][[*][+][:]]=value
...]
[-v[cdfimrtw]] [-m[trae]] [-ABcdeEghiknpqrsStTuVxX] [target ...]
The dmake parallel make option is -P# and not -j#
This type of inconsistency is why moving to Module::Build
with its C compiler + perl requirements to configure and
build is attractive. E.g., not all make programs have an
option to give version information and the options are not
the same across make programs.
Cheers,
Chris
