BUILD: haproxy: fix build error when RLIMIT_AS is not set
authorWilly Tarreau <w@1wt.eu>
Thu, 2 Jul 2020 13:38:35 +0000 (15:38 +0200)
committerChristopher Faulet <cfaulet@haproxy.com>
Fri, 3 Jul 2020 17:03:55 +0000 (19:03 +0200)
As reported in issue #724, openbsd fails to build in haproxy.c
due to a faulty comma in the middle of a warning message. This code
is only compiled when RLIMIT_AS is not defined, which seems to be
rare these days.

This may be backported to older versions as the problem was likely
introduced when strict limits were added.

(cherry picked from commit ab8b6a45be2f76efb28f7f0ad18b69549c77b4d6)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>

src/haproxy.c

index 42f898f..83131eb 100644 (file)
@@ -3125,7 +3125,7 @@ int main(int argc, char **argv)
                                        exit(1);
                        }
                        else
-                               ha_warning("[%s.main()] Cannot fix MEM limit to %d megs.",
+                               ha_warning("[%s.main()] Cannot fix MEM limit to %d megs."
                                           "This will fail in >= v2.3\n",
                                           argv[0], global.rlimit_memmax);
                }