Bug 210381

Summary:	Building ^/releng/10.3 from 10.3-RELEASE-p4 fails: don't know how to make lzma12.h. Stop
Product:	Base System	Reporter:	Enji Cooper <ngie>
Component:	bin	Assignee:	Xin LI <delphij>
Status:	Closed Unable to Reproduce
Severity:	Affects Many People	CC:	bigwoody2
Priority:	---
Version:	10.3-RELEASE
Hardware:	Any
OS:	Any

Description Enji Cooper freebsd_committer

2016-06-19 05:08:07 UTC

It looks like lzma12.h isn't being installed properly:

--- cms_asn1.h ---^M
--- lib.includes__D ---^M
make[5]: make[5]: don't know how to make lzma12.h. Stop^M
^M
make[5]: stopped in /usr/src/lib/liblzma^M
*** [_sub.buildincludes] Error code 2^M
^M
make[4]: stopped in /usr/src/lib^M
1 error^M
^M
make[4]: stopped in /usr/src/lib^M
--- kerberos5.includes__D ---^M
cmp -s cms_asn1.hx cms_asn1.h 2> /dev/null || cp cms_asn1.hx cms_asn1.h^M
--- lib.includes__D ---^M
*** [includes] Error code 2^M
$ svn diff lib/liblzma/Makefile ^/stable/10/lib/liblzma/Makefile
$ svn blame lib/liblzma/Makefile | grep 'lzma12.h'
292588    delphij               lzma12.h \

Comment 1 Enji Cooper freebsd_committer

2016-06-19 05:08:37 UTC

$ svn info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn.freebsd.org/base/releng/10.3
Relative URL: ^/releng/10.3
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 302017
Node Kind: directory
Schedule: normal
Last Changed Author: delphij
Last Changed Rev: 301301
Last Changed Date: 2016-06-03 22:46:52 -0700 (Fri, 03 Jun 2016)

Comment 2 Xin LI freebsd_committer

2016-06-19 06:26:45 UTC

I highly doubt this because the way how freebsd-update is built is exactly creating a jail, apply patches and build from scratch, twice.

I'm starting a build from scratch on an isolated environment to verify.

Comment 3 Xin LI freebsd_committer

2016-06-19 07:26:16 UTC

Unable to reproduce (from 10.3-RELEASE base.txz to releng/10.3).

Comment 4 Enji Cooper freebsd_committer

2016-06-19 08:20:29 UTC

I confirmed that the environment was the culprit.

Running "svn status" on /usr/src, it seems that the svn switch operation was interrupted (a large number of paths were reporting "S"). Running "svn switch ^/releng/10.3" fixed the problem. make buildworld buildkernel subsequently completed successfully on picasso.local.