On Mon, Aug 16, 2010 at 5:04 PM, Andy Dougherty <dough...@lafayette.edu> wrote:
> On Mon, 16 Aug 2010, Joshua ben Jore wrote:
>
>> On Sat, Aug 14, 2010 at 4:18 PM, Daniel Pfeiffer <occi...@t-online.de> wrote:
>> > From your doc:
>> > MAKE ... Defaults to $Config{make}.
>> >
>> > It should default to not being changed, so as to allow the user to choose
>> > which make he wants to use.
>
> The value for $Config{make} is documented as being not useful, but it
> appears that Win32 does reliably set it to something relevant. This can
> be important for generating the correct makefiles, but I agree that as
> long as $Config{make_set_make} eq '#', then it would seem that it doesn't
> need to be explicitly set in the generated makefiles. I don't know why it
> is; nor do I know what would break if anyone tried removing it. It might
> be interesting to test and see.
>
>> About $Config{gmake} and not $Config{make},
>>
>> Just FYI, Perl is apparently buggy in that it will set $Config{gmake}
>> even when there isn't an appropriate thing there. Tools like EU::MM
>> must be able to handle a Perl %Config that lies a little because
>> unfortunately, Perl's %Config lies a little.
>
> No, this is not a bug. Please read the Config.pm documentation for
> $Config{gmake}.
Fascinating. I didn't realize Config had documentation and it is weird
that we're exporting things we're actually calling "useless." Same
thing for $Config{make} apparently. Also fascinating are the seemingly
other useless values I thought were actually meaningful.
I guess I've got to fix up my Alien::Judy code now that was using that
value. It sure /looked/ like the value I'd want to have depended on.
Josh
