Re: [PATCH] Re: 4.90RC1 doesn't compile on FreeBSD

[Kris Katterjohn <katterjohn () gmail com>]

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

Daniel Roethlisberger wrote:
> Fyodor <fyodor () insecure org> 2009-06-29:
> > On Sat, Jun 27, 2009 at 02:59:17PM +0200, Daniel Roethlisberger wrote:
> > > Fyodor <fyodor () insecure org> 2009-06-26:
> > >
> > > Patch attached.  With gmake installed, invoking `make` will
> > > automatically invoke `gmake` on the same target(s).  Without
> > > gmake installed, you get this:
> > Thanks, this looks good.  Do you know if the make on FreeBSD, Solaris,
> > OpenBSD, and NetBSD all accept this 'BSDmakefile' name and give it
> > precedence over "Makefile"?
>
> FreeBSD and OpenBSD both have a make(1) which uses "BSDmakefile"
> in precedence of "makefile" and "Makefile".  NetBSD and Solaris
> don't.
>
> I don't think it is feasible to write a Makefile compatible with
> all implementations of make(1), but maybe that's being too
> pessimistic.

What about this?

GNU make checks for GNUmakefile before anything else, just like the BSD make
in FreeBSD and OpenBSD apparently checks for BSDmakefile first.

So:

1) Move our current Makefile to GNUmakefile
2) Create a new Makefile/makefile which simply calls gmake on the GNUmakefile

Why?

1) GNU make (Linux make, gmake, whatever) will call GNUmakefile first, so it
ends there just like it should
2) *Every* non-GNU make should use the Makefile, which calls gmake, which is
what we want

Cheers,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKSTutAAoJEEQxgFs5kUfuVWQQAMbkqZjNKEF9oq1zTldmdarM
glmrC8WHYdcKz5euKWi9fjFD2T7cVfRr5cnKFoGGBydD7snJ7rFZf4ISaiF5hhmE
DuKYzXV5sGJTt4gUFvkFSCfIA1zm+YMCHCYRSvt3b/X8eKSLureeDiVt1K3BLjLN
7kE3DZYhoMItIQdAaNIY7ZPpWacH+knx+EEQOLkM0avPclcnx3dCr/YZYbu8Y7yp
r58TaoBB1NA+pEuOQvh9Y+dDGZz5Lh1e1pj+e6qpDMHoSL5PJNjX7/Ta59aKSKuv
bW7OqGqKRO1Kyyc0oV+8/icwSO9PBeJqNjwHWVgjAxTjEPYk4lS267WdX5LL6V+g
hKLZFzVPn6DhB23pyMyr5JqrvYTsEUgA2iJl3C1Qvp+5q6gaxXbN6ZRLwyzDbIPi
a4bD+3FyESxrexf3ktHGObBOUKn3YCpuDWDOQ792sYELyQuq3YcPo5CbOdZ8B11j
oCqEq0pHTUG6onJ4uslgISSXMV4/r41Imt3ix1rxAqtsCEgRj0B0bd8x+Hc3j8Hq
4Wq1ZzOG1Bnd4NGzduo+KwL1oiDOhk4ZCfl3xs99/ic1tUlyUxAYdTcyUJCPFm1o
zy10TEdaw+Ja4QeEJ8hGBz+xi4bIHDSPrWNDJcBc2ILtq+4NXUyOevVW4BlJ/3Bx
62Xwxhn1BxHkQ3WYiRdI
=6kkO
-----END PGP SIGNATURE-----

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org