Repository navigation
haproxy 2.4.3 fails to start, complains about CFLAGS used during build #313
Description
Activity
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=1With 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.
- added a commit that references this issue
on Aug 31, 2021 Ok, the fixed
haproxy-2.4.3nb1is now available in the trunk package set. Sorry for the mess.Thanks!
- added a commit that references this issue
on Sep 21, 2021 - added a commit that references this issue
on Sep 1, 2022 - added a commit that references this issue
on Nov 15, 2022 - added 2 commits that reference this issue
on Dec 18, 2022 - added 2 commits that reference this issue
on Feb 7, 2024 31 remaining items
- added 9 commits that reference this issue
on May 14, 2026 - added 2 commits that reference this issue
on May 22, 2026 - added a commit that references this issue
on May 24, 2026 - added a commit that references this issue
on Jun 8, 2026 - added a commit that references this issue
on Jun 23, 2026 - added a commit that references this issue
on Aug 25, 2026
After update to haproxy 2.4.3 this morning, it failed to start. From the service log:
This may be relevant - haproxy/haproxy@1335da38f4 - discussion of checking for the compiler option -fwrapv.
Downgrading to 2.4.2 got us back on the air for now.