[Bug 279120] devel/kronosnet: fails to build on latest 15 as of today
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 18 May 2024 05:02:29 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279120
Bug ID: 279120
Summary: devel/kronosnet: fails to build on latest 15 as of
today
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: egypcio@FreeBSD.org
Reporter: fdinitto@redhat.com
Assignee: egypcio@FreeBSD.org
Flags: maintainer-feedback?(egypcio@FreeBSD.org)
Hi,
I am the upstream maintainer for knet and our CI has detected a failure to
build kronosnet on FreeBSD-devel.
After some research, I found out that also your port CI has been reporting the
same issue here:
https://www.mail-archive.com/freebsd-pkg-fallout@freebsd.org/msg2310798.html
Upon further inspections, 2 problems come up:
1) gcc FORTIFY_SOURCE is currently broken (ssp.h is provided by gcc)
I didn´t have time to dig specifically into this problem, but it was not an
issue last week, and knet code has not changed in between.
2) knet detection of FORTIFY_SOURCE support is also broken
As I am driving the fix into a stable release, you can grab the fix here:
https://github.com/kronosnet/kronosnet/pull/427/commits/8755fcf5cea8a52ddcd1f3a9194e97c392e9d2e4
as a secondary note, I see that the knet port specify "USE_GCC= yes". We do
test knet with clang as part of our CI run and it is gating. If clang build
doesn´t pass, we can´t merge any patch.
If you prefer to switch to clang, that would be just fine with upstream.
Cheers
Fabio
--
You are receiving this mail because:
You are the assignee for the bug.