The port builds OK for me with OpenSSL 1.1.0 as well as OpenSSL 1.1.1. Am I missing something? https://keg.brnrd.eu/data/111amd64-default-openssl110/2018-08-17_12h10m13s/logs/apache-xml-security-c-2.0.1.log https://keg.brnrd.eu/data/111amd64-default-openssl111/2018-08-14_10h01m04s/logs/apache-xml-security-c-2.0.1.log Perhaps this was fixed in an update?
Only port i see similar to this one listed is apache-xml-secuity-c and it was updated 5 weeks ago
(In reply to Nathan from comment #1) Sorry about that, meant security/apache-xml-security-c indeed Can you please test to confirm with security/openssl111 and confirm build and run are OK? I can do the commit.
(In reply to Bernard Spil from comment #2) Yep sure will
There is a build issue but will try work on it when I get on my pc at home
Got to build but got to fix linker somehow as normal routes isn’t working for me yet
Ok no linker issue after all. The only change it needs is ${OPENSSLLIB} to /use/local/lib. After that it built for me
(In reply to Nathan from comment #6) Need to strip a library file as well. Sorry on phone so makes it harder to fix and upload
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229022 May can be closed as it involves this one
Created attachment 197082 [details] Prepare for LLD on i386 Tested in 12-current(i386) built fine; I am unsure how this port works exactly but just executing the commands did not give segfaults
BTW The changes on the patches are because I did make patch then make makepatch to generate patches correctly
Created attachment 197083 [details] Prepare for LLD on i386; Strip library file Forgot to strip the library file, this corrects it
security/apache-xml-security-c builds fine with OpenSSL 1.1.1 (ports r487344) with the base version and security/openssl111. Next time CC'ing the maintainer to give some feedback might help. ;-)
Version 2.0.0 added support for OpenSSL 1.1 [1]. Girgen (maintainer) updated the port to 2.0.1 in ports r476595. Tobias removed the BROKEN in ports r487344 (this PR was not referenced), so is the resolver of this issue. [1] https://issues.apache.org/jira/browse/SANTUARIO-460