-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tarball: building without pandoc fails after make clean; configure
#284
Comments
When building from a tarball, pre-created man pages are preset. Yet `make clean` clobbers them, leaving their target directory intact. Therefore, the next configure call will try to build man pages even if pandoc isn't available. Fix this by cleaning the man pages only if they can be recreated by the presence of pandoc. Fixes tpm2-software#284 Signed-off-by: Moritz Barsnick <[email protected]>
When building from a tarball, pre-created man pages are preset. Yet `make clean` clobbers them, leaving their target directory intact. Therefore, the next configure call will try to build man pages even if pandoc isn't available. Fix this by cleaning the man pages only if they can be recreated by the presence of pandoc. Fixes tpm2-software#284 Signed-off-by: Moritz Barsnick <[email protected]>
I suggest creating a |
Please feel free to do so, and take my change only as a suggestion. I needed to implement a minimal change that looked logically okay and fixed our Yocto (re-)builds. |
When building from a tarball, pre-created man pages are preset. Yet `make clean` clobbers them, leaving their target directory intact. Therefore, the next configure call will try to build man pages even if pandoc isn't available. Fix this by cleaning the man pages only if they can be recreated by the presence of pandoc. Fixes tpm2-software#284 Signed-off-by: Moritz Barsnick <[email protected]>
When using the source tarball, and building without pandoc, builds fail after
make clean
with a subsequent re-configure
.This is what happens when building multiple times in a Yocto workspace, e.g. using this recipe in the meta-security layer:
https://git.yoctoproject.org/meta-security/tree/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.1.0.bb?h=kirkstone&id=353078bc06c8b471736daab6ed193e30d533d1f1
When re-using the workspace, Yocto will issue a
make clean
before runningautoreconf
,./configure
and compiling.Since the tarball includes the pre-processed man pages under
man/man{1,3}/
, andmake clean
erases the man page files (but not the directory), the subsequent./configure
picks upHAVE_MAN_PAGES
:tpm2-tss-engine/configure.ac
Line 139 in 766505b
and tries to build them, even when pandoc is not available. This results in a build failure:
from this Makefile line:
tpm2-tss-engine/Makefile.am
Lines 205 to 206 in 766505b
The question is whether the pre-processed man pages just should not be deleted if they cannot be built, or whether the
HAVE_MAN_PAGES
condition should be determined differently.The text was updated successfully, but these errors were encountered: