Hi,
I've been trying to build GnuPG 2.2.19 and 2.2.20 today and found that, with ./configure --disable-gpg, and with --disable-all-tests in addition too, I got the error make[4]: *** No rule to make target '../../g10/gpg.exe', needed by 'all- local'. Stop. make[4]: Leaving directory '/home/john/foo/gnupg-2.2.20/tests/openpgp' This isn't specific to Windows cross-building. Doing it natively got the similar but different error gcc -Wall -Wno-pointer-sign -Wpointer-arith -g -O2 ../../g10/gpg.c -o ../../g10/gpg ../../g10/gpg.c:22:10: fatal error: config.h: No such file or directory 22 | #include <config.h> | ^~~~~~~~~~ compilation terminated. make[3]: *** [<builtin>: ../../g10/gpg] Error 1 make[3]: *** Waiting for unfinished jobs.... mv -f .deps/fake-pinentry.Tpo .deps/fake-pinentry.Po make[3]: Leaving directory '/home/john/bar/gnupg-2.2.20/tests/openpgp' I'd also like to inform you that [1] says bug reports should be sent to this mailing list, in case that's outdated in light of dev.gnupg.org [1] https://www.gnupg.org/download/git.html _______________________________________________ Gnupg-devel mailing list [hidden email] http://lists.gnupg.org/mailman/listinfo/gnupg-devel |
On Tue, 26 May 2020 21:49, John Scott said:
> I've been trying to build GnuPG 2.2.19 and 2.2.20 today and found that, with > ./configure --disable-gpg, and with --disable-all-tests in addition Oh well, I forgot about that option. I doubt that it makes any sense to build without gpg becuase gpg is also used by other components indirectly. I better remove the --disable-gpg feature. Is there a special reason why you do this? > make[4]: *** No rule to make target '../../g10/gpg.exe', needed by 'all- > local'. Stop. Obvious. The tests require that all programs have been built. --disable-all-tests is not what one would expect - it is actually the default. While preparing a distribution we use --enable-all-tests to run a bunch or extra tests which don't make much sense for non-maintainers. But, right: The --disable-COMPONENT options and the test suite don't work well together. We should do something about it; see https://dev.gnupg.org/T4960 > gcc -Wall -Wno-pointer-sign -Wpointer-arith -g -O2 ../../g10/gpg.c -o > ../../g10/gpg > ../../g10/gpg.c:22:10: fatal error: config.h: No such file or directory config.h is a built file; you forgot to run configure. > I'd also like to inform you that [1] says bug reports should be sent to this > mailing list, in case that's outdated in light of dev.gnupg.org That's okay; only a few eyes will see bug reports at dev.gnupg.org; on the ML you have a good chance that others already know a solution or are interested in the same problem. For the development branch it is quite normal that certain bugs show up and are fixed some time later. Shalom-Salam, Werner _______________________________________________ Gnupg-devel mailing list [hidden email] http://lists.gnupg.org/mailman/listinfo/gnupg-devel |
On Friday, May 29, 2020 8:08:11 AM EDT Werner Koch wrote:
> Is there a special reason why you do this? I didn't need the gpg binary, for my purpose I just needed a very minimal gpgsm, Dirmngr and gpg-agent build that need not have OpenPGP support. --disable-gpg shows both config.status: creating tests/openpgp/Makefile ... GnuPG v2.2.20 has been configured as follows: Revision: 5094bb08e (20628) Platform: GNU/Linux (x86_64-pc-linux-gnu) OpenPGP: no > > gcc -Wall -Wno-pointer-sign -Wpointer-arith -g -O2 ../../g10/gpg.c -o > > ../../g10/gpg > > ../../g10/gpg.c:22:10: fatal error: config.h: No such file or directory > > config.h is a built file; you forgot to run configure. I did not, I ran configure to do --disable-gpg. Doing ./configure --disable-gpg and running make in a fresh tree gets me the error again. _______________________________________________ Gnupg-devel mailing list [hidden email] http://lists.gnupg.org/mailman/listinfo/gnupg-devel |
Free forum by Nabble | Edit this page |