Bug #2450
closed
building 3.2 release on master fails
0%
Description
Using master of October 30 buildworld of 3.2 release fails,
see below for make output.
It seems like problem is that new make (aka bmake)
isn't backward compatible with old make,
e.g. .makeenv command isn't supported.
(after adding this command to bmake, buildworld fails later in build)
thomas
$ head -56 /usr/src/share/mk/bsd.cpu.mk | tail -2
.makeenv CCVER
.makeenv HOST_CCVER--
make: "/usr/src/share/mk/bsd.cpu.mk" line 55: Unknown directive
make: "/usr/src/share/mk/bsd.cpu.mk" line 56: Unknown directive
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/src
- [buildworld] Error code 1
make: stopped in /usr/src
make: stopped in /usr/src
Updated by marino over 11 years ago
The changes to the master branch makefiles can be backported.
It was envisioned that 3.2 would only be built by earlier versions, not later versions but I think we can do a "minimal" backport that will work with a full buildworld and buildkernel command. (iow don't bother to support quickworld)
Updated by marino over 11 years ago
In order to test a fix, can you confirm that you are attempting to downgrade worlds?
In other words, you are on master, and then using git you switch /usr/src to the release 3.2 branch, and then attempt to build world?
Updated by marino over 11 years ago
- Status changed from New to Closed
It is possible to build RELEASE 3.2 from master now.
Also confirmed building from previous to 3.2.1 release also works.
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/a8a5ffd44fb4125eb0ecd27ace70257e31dd23b4
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/59620cdf5e51b69ddb60f977317c7aa9d6dc86d5
first commit is cherry-pick, second commit is unique to release 3.2.
Only the minimum number of bmake changes were brought in to support parallel-building of world. Without -j, only the bsd.cpu.mk file needed updating.