On 07/22/18 15:53, Matthew Macy wrote:
> That would only fix it if svn weren't installed.
Oops, good point. Thanks for fixing this, your commits look good to me.
Colin Percival
> On Sun, Jul 22, 2018 at 9:31 AM, Colin Percival wrote:
>> On 07/22/18 08:04, Rodney W. Grimes wrote:
Build sti
That would only fix it if svn weren't installed.
On Sun, Jul 22, 2018 at 9:31 AM, Colin Percival wrote:
> On 07/22/18 08:04, Rodney W. Grimes wrote:
>>> Build still works, but you're assuming that developers only use svn.
>>
>> No, he correctly assumed that RELEASE engineering only uses svn/svnli
On 07/22/18 08:04, Rodney W. Grimes wrote:
>> Build still works, but you're assuming that developers only use svn.
>
> No, he correctly assumed that RELEASE engineering only uses svn/svnlite
> for building release images. This Makefile is for production of
> official AMIs, official stuff always u
> Build still works, but you're assuming that developers only use svn.
No, he correctly assumed that RELEASE engineering only uses svn/svnlite
for building release images. This Makefile is for production of
official AMIs, official stuff always uses svn.
> make[1]: "/usr/home/mmacy/devel/freebsd
Build still works, but you're assuming that developers only use svn.
make[1]: "/usr/home/mmacy/devel/freebsd/Makefile.inc1" line 343:
SYSTEM_COMPILER: libclang will be built for bootstrapping a
cross-compiler.
make[1]: "/usr/home/mmacy/devel/freebsd/Makefile.inc1" line 348:
SYSTEM_LINKER: libclang
Author: cperciva
Date: Sat Jul 21 22:54:43 2018
New Revision: 336593
URL: https://svnweb.freebsd.org/changeset/base/336593
Log:
Use svn or svnlite, or ${SVN_CMD} if set, for extracting the SVN branch
and revision number announced in SNS notifications about new EC2 AMIs.
While I'm here, in