Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] [PATCH 1/4] Check for gmake, falling back to make

  • Subject: [Frama-c-discuss] [PATCH 1/4] Check for gmake, falling back to make
  • From: richard.bonichon at (Richard Bonichon)
  • Date: Sat, 27 Feb 2010 21:05:51 +0100
  • In-reply-to: <>
  • References: <>


On Sat, Feb 27, 2010 at 8:41 PM,  <fr.inria.gforge.lists at> wrote:
> FreeBSD (and anything that isn't Linux or OS X) do not call GNU make
> 'make'. This patch checks explicitly for 'gmake', falling back to
> 'make' if it cannot be found. Of course, if it falls back to 'make'
> and 'make' does not denote GNU make, the '-v' check later will fail
> catastrophically. Is there really a good reason to check for GNU
> make explicitly?

Frana-C's makefiles use GNU make extensions. In this respect, it makes
sense to check for GNU make.
You could also use set the MAKE variable on the CLI before calling
configure (eg MAKE=gmake ./configure).

Thanks for all the patches (maybe you could have use Frama-C's BTS at

Actually, the configuration issues (due to the use of == instead of =)
you are dealing with are already fixed in the the svn tree.
It is rather uncanny that only FreeBSD's default sh caught the use of
non-posix test extensions (this is okay with debian's dash or
OpenBSD's sh)

Again thanks for your diffs.

Richard Bonichon