Almost certainly the -fno-common problem with clang 11. This now defaults to -fno-common, which causes multiply defined symbols at link time if something is declared global in more than one module (instead of extern in all but one module). There is a similar problem with gcc.
Declaring -fno-common on your existing build will trigger the problem. What you are seeing (success) is because clang 11 isn't actually in -CURRENT yet. When I fixed my ports, I had to install (build) clang 11 (from llvm11) to do the testing. On Tue, 1 Sep 2020 19:35:44 +1000 Sean Greven <sean.gre...@gmail.com> wrote: > Hi there > > I have received a number of messages from pkg-fallout regarding the > port I maintain, and pkg-fallout maintains that my port is broken. > > The really strange thing here is that I am able to build it in all the > versions up till 13.0-CURRENT. > The port builds without any errors. Any one with any ideas on how to > troubleshoot this further? > > Below is the last piece of the error returned from pkg-fallout. > > cc: error: linker command failed with exit code 1 (use -v to see > invocation) *** [fwknop] Error code 1 > > make[3]: stopped in > /wrkdirs/usr/ports/security/fwknop/work/fwknop-2.6.10/client > 1 error > > make[3]: stopped in > /wrkdirs/usr/ports/security/fwknop/work/fwknop-2.6.10/client > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the > failure to the maintainer. > *** Error code 1 > _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
