gmake required for C extensions

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Voelker, Bernhard wrote:
> Hi,
> 

...

> Following the URL, I tried a simple `make`:
> 
> 
>   $ make
>   make: Fatal error in reader: Makefile, line 175: Unexpected end of line seen
> 
> 
> It seems that GNU make is required.
> Fortunately, I had compiled that a few months ago for another software,
> but IMHO it would be nice if bzr would not rely on it.
> Is there an official statement about this?
> 
> BTW: gmake ran fine (with a bunch of warnings).
> 
> Have a nice day,
> Berny
> 

I don't know specifically the differences between regular make syntax
and gmake syntax. Line 175 looks like:

DOC_WEBSITE_BUILD := build_doc_website

My guess is the ':=' is to blame, versus just '='. I don't remember the
specific difference (I thought it had to do with when the variable is
bound, and when it is expanded / how arguments passed to make are handled.)

As I don't have anything *but* gnu make here, I certainly couldn't be
sure that I could fix the make file.

For things like ":=" I don't think we require it, so updating it to
avoid depending on gnu make would be fine. However, there are other
things that we might use, like $(wildcard...) that make our lives a lot
easier. If those are extensions then we will probably just live with it.

In summary, if you want to try to put a patch together, I'd be happy to
review it. If it is minor syntax tweaks, then great. If it changes some
fundamental structures so that we have to start manually tracking all
files, then we probably won't.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrXOHsACgkQJdeBCYSNAANdBwCfZyPprMhVEzZ0JEktZi7fKRNq
xtcAn04oB5zxJ4tx+JeI9oC/BdnCSARn
=rZ4u
-----END PGP SIGNATURE-----