Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Feb 2015 00:05:57 +0100
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Ian Lepore <ian@freebsd.org>
Cc:        Greg 'groggy' Lehey <grog@FreeBSD.org>, arch@FreeBSD.org, current@FreeBSD.org
Subject:   Re: [RFC] Removin the old make
Message-ID:  <20150210230557.GV29891@ivaldir.etoilebsd.net>
In-Reply-To: <1423609456.80968.32.camel@freebsd.org>
References:  <20150210223854.GT29891@ivaldir.etoilebsd.net> <20150210224937.GE58387@eureka.lemis.com> <20150210225941.GU29891@ivaldir.etoilebsd.net> <1423609456.80968.32.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--6h64vBu9tReNbGLX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 10, 2015 at 04:04:16PM -0700, Ian Lepore wrote:
> On Tue, 2015-02-10 at 23:59 +0100, Baptiste Daroussin wrote:
> > On Wed, Feb 11, 2015 at 09:49:37AM +1100, Greg 'groggy' Lehey wrote:
> > > On Tuesday, 10 February 2015 at 23:38:54 +0100, Baptiste Daroussin wr=
ote:
> > > > Hi,
> > > >
> > > > I would like to start using bmake only syntax on our infrastructure=
 for that I
> > > > want to make sure noone is using the old make, so I plan to remove =
the old make
> > > > from base, I plan to do it by Feb 16th.
> > >=20
> > > How does this affect non-system Makefiles that depend on pmake?  Is
> > > bmake completely upward compatible?
> >=20
> > There are very few issues, not that fmake is available from ports, I th=
ink 99%
> > of the compatibility are preserved I know about a couple of incompatibi=
lities
> > that are bothering me in ports (for the infrastructure) but I would say=
 this is
> > very much a corner case
> >=20
> > Bapt
>=20
> By far the biggest incompatibility I've run into is the change from :U
> and :L to :tu and :tl, mostly because any existing makefiles that
> contain :U or :L variable modifiers just silently do the wrong thing
> under bmake.  It's especially annoying because :L is really common in
> fmake and its meaning in bmake is all but useless.
>=20
Ah yes I forgot that one :) which is the reason why I have blocked migratio=
n to
bmake for a while :)

Still fmake is available via ports so might not be a problem

Best regards,
Bapt

--6h64vBu9tReNbGLX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlTajtUACgkQ8kTtMUmk6EzyxwCeI9Lt4UPGBa4I6GP0Z/d7Lby5
wscAn3z73P1UI1G7vKpqjYBy4LiEbmg0
=8uZ8
-----END PGP SIGNATURE-----

--6h64vBu9tReNbGLX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150210230557.GV29891>