Nuno Teixeira

2.2.16: error: incompatible function pointer types passing 'gboolean (GtkWindow *)'

2.2.2 man page says related to --pinentry-mode: NOTE: Contrary to previous versions of duplicity, this option will also be honored by GnuPG 2 and newer versions. If GnuPG 2 is in use, duplicity passes the option --pinentry-mode=loopback to the the gpg process unless --use-agent is specified on the duplicity command line. This has the effect that GnuPG 2 uses the agent only if --use-agent is given, just like GnuPG 1. Does it make sense about using this option and error msg: duplicity.cli_util.CommandLineError:...

fatal error: 'alloca.h' file not found

Hello, Committed in https://cgit.freebsd.org/ports/commit/?id=2f3cbb880dc06413014f6661caea4e046bf36c5f Thanks

Hello Allen, graphics/libemf port uses gnu configure and I'm using workaround: USES=compiler:c++14-lang (to tell ports framework that a c++14 capable compiler is needed) USE_CXXSTD=c++14 (to force -std=c++14 on compiler) IMHO there is no need to change to cmake just because of forcing -std, but cmake is a newer build system. Since clang16 have landed a lot of programs have broken because of c++17 default standard and solutions are being searched to fix code so c++17 compliant can be achieved when...

Hello Allen, graphics/libemf port uses gnu configure and I'm using workaround: USES=compiler:c++14-lang (to tell ports framework that a c++14 capable compiler is needed) USE_CXXSTD=c++14 (to force -std=c++14 on compiler) IMHO there is no need to change to cmake just because of forcing -std, but cmake is a newer build system. Since clang16 have landed a lot of programs have broken because of c++17 default standard and solutions are being searched to fix code so c++17 compliant can be achieved when...

build fails on clang16

glib2 deprecated declarations failing on clang16