Date: Tue, 17 Jun 2014 15:14:40 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Craig Rodrigues <rodrigc@FreeBSD.org> Cc: Marcel Moolenaar <marcel@FreeBSD.org>, Brooks Davis <brooks@FreeBSD.org>, Warner Losh <imp@bsdimp.com>, freebsd-current Current <freebsd-current@FreeBSD.org> Subject: Re: Problems building FreeBSD 9.2 on FreeBSD 10 Message-ID: <20140617221440.99644580A1@chaos.localdomain> In-Reply-To: <CAG=rPVeBgWS=vMGxSmX8O4QWW77XC2mqDgaiNrFsGrzg47UQYQ@mail.gmail.com> References: <CAG=rPVct-HzOksM2KQvPuOdf4zgZo__=Oannh0x%2B_JVHEzQyyw@mail.gmail.com> <CAG=rPVfkGa7=n-TSqcnP574ry0Au2THbqvAZJfKD5OK9a1FBNw@mail.gmail.com> <20140617200551.07542580A1@chaos.localdomain> <CAG=rPVeBgWS=vMGxSmX8O4QWW77XC2mqDgaiNrFsGrzg47UQYQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Why not use fmake in that scenario? > >That might work. Is using the devel/fmake port sufficient for using fmake? So long as it is recent enough to have :tu and :tl I would expect so. >If I typed "make something", is there a way inside the make environment to >detect if bmake or fmake was invoked, and error out appropriately? You can test for bmake with .if defined(.PARSEDIR) lack of that means fmake.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140617221440.99644580A1>