Closed dhull closed 3 years ago
Yeah, the build-from-tar expects a release-style tar. When building nightlies I have a Jenkins job that grabs them from git and packs them up like so:
DATE=$(date "+%Y-%m-%d_%H-%M-%S")
REV=$(git rev-parse HEAD)
DIR=emacs-$DATE-$REV
git archive --prefix="$DIR/" HEAD | tar x
(cd $DIR && ./autogen.sh && make docs && make distclean)
tar cjf $DIR.tar.bz2 $DIR
The resulting tar gets fed into another Jenkins job that runs build-emacs-from-tar
. This is so releases, pretests, and nightlies are all built consistently.
Sorry to make you debug the --without-pk11-kit
bug. I committed the same fix last week but hadn't pushed it to github (my Jenkins reads from my local private repo). It's pushed now.
The libxml2 thing is weird. Until recently I was building on 10.6, 10.8, 10.9, and 10.10 and none of them needed that. A quick test on 10.14 failed. I don't normally built there, so that's why I haven't encountered it yet.
I applied your readme change.
I found the incantation to fix the missing libxml2 headers:
sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target /
(I just ran into the same issue while bringing up a mojave build machine).
The
build-emacs-from-tar
script failed to build emacs-26.1.90.tar.gz on my machine without the following changes.configure
script so it was necessary to runautogen.sh
to create it.LIBXML2_CFLAGS
when running configure to work around this problem. I see that the configure script has a macOS-specific test for libxml2 that looks like it should have worked, but it didn't.