Closed drboone closed 3 years ago
The haproxy Makefile has quite a bit of CFLAGS manipulation in it. Given what it needs, this might be the better way to pass in the pkgsrc CFLAGS setting:
diff --git a/net/haproxy/Makefile b/net/haproxy/Makefile
index 8cc3b1b6314..6be440674de 100644
--- a/net/haproxy/Makefile
+++ b/net/haproxy/Makefile
@@ -13,7 +13,7 @@ USE_LANGUAGES= c
USE_TOOLS+= gmake
BUILD_MAKE_FLAGS+= ADDLIB=${COMPILER_RPATH_FLAG}${PREFIX}/lib
BUILD_MAKE_FLAGS+= CC=${CC:Q}
-BUILD_MAKE_FLAGS+= CFLAGS=${CFLAGS:Q}
+BUILD_MAKE_FLAGS+= DEBUG_CFLAGS=${CFLAGS:Q}
BUILD_MAKE_FLAGS+= LDFLAGS=${LDFLAGS:Q}
BUILD_MAKE_FLAGS+= TARGET=${TARGET}
BUILD_MAKE_FLAGS+= USE_REGPARM=1
With this change, haproxy does build, package, and not throw errors at startup.
Ugh, thanks. I've applied this patch upstream and will get a trunk build started as soon as it's merged to git.
Ok, the fixed haproxy-2.4.3nb1
is now available in the trunk package set. Sorry for the mess.
Thanks!
After update to haproxy 2.4.3 this morning, it failed to start. From the service log:
This may be relevant - https://github.com/haproxy/haproxy/commit/1335da38f4 - discussion of checking for the compiler option -fwrapv.
Downgrading to 2.4.2 got us back on the air for now.