GNU bug report logs - #35848
Should automake use gmake by default if exists?

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Karl Berry <karl <at> freefriends.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#35848: closed (Should automake use gmake by default if exists?)
Date: Sat, 15 Feb 2020 02:40:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 14 Feb 2020 19:39:48 -0700
with message-id <202002150239.01F2dm4o004968 <at> freefriends.org>
and subject line Re: bug#35848: Should automake use gmake by default if exists?
has caused the debbugs.gnu.org bug report #35848,
regarding Should automake use gmake by default if exists?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
35848: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35848
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: libor.bukata <at> oracle.com
To: bug-automake <at> gnu.org
Subject: Should automake use gmake by default if exists?
Date: Tue, 21 May 2019 15:53:40 +0200

Hi,

automake expects GNU make to support dependency tracking.

On Solaris it works well if MAKE variable is set to gmake during the 
configuration, otherwise, it fails with the following error.

config.status: error: Something went wrong bootstrapping makefile fragments
    for automatic dependency tracking.  Try re-running configure with the
    '--disable-dependency-tracking' option to at least be able to build
    the package (albeit without support for automatic dependency tracking).
See `config.log' for more details

My suggestion is to use gmake by default if the command exists, 
otherwise fallback to make command. It could improve the overall user 
experience since the user would not need to search a solution 
(./configure MAKE=gmake) every-time this error is encountered.

Currently, it seems that the default MAKE value (${MAKE-make}) is 
hard-coded in four m4 files. Would it be possible to set the default 
MAKE value dynamically at the beginning of the configuration phase based 
on the existence of gmake and make commands? The m4 files could then 
expect that MAKE variable is defined from the configure script.

Note that we used automake 1.16.1 on Solaris 11.4 but the issue is also 
reproducible with older automake versions.

Thanks,
Libor

[Message part 3 (message/rfc822, inline)]

From: Karl Berry <karl <at> freefriends.org>
To: libor.bukata <at> oracle.com
Cc: nbowler <at> draconx.ca, automake-patches <at> gnu.org, 35848 <at> debbugs.gnu.org
Subject: Re: bug#35848: Should automake use gmake by default if exists?
Date: Fri, 14 Feb 2020 19:39:48 -0700

Hi Libor - back on your improvement to the failed dependency tracking
message, from last May (sorry):

     From: Libor Bukata <libor.bukata <at> oracle.com>
     Date: Thu, 23 May 2019 12:31:31 +0200
     ...
+    AC_MSG_FAILURE([Something went wrong during bootstrapping of makefile
+    fragments for automatic dependency tracking. If the GNU make is not
+    used by default, consider to rerun the configure script with MAKE="gmake".
     ...

I've applied this patch, modulo a few tweaks to the wording. Thanks! -k

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.