From: Peter Korsgaard <peter@korsgaard.com>
To: Aleksandr Makarov <aleksandr.o.makarov@gmail.com>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/haproxy: fix runtime 'FATAL ERROR: invalid code detected -- cannot go further'
Date: Thu, 29 Feb 2024 15:21:34 +0100 [thread overview]
Message-ID: <87edcvic5t.fsf@48ers.dk> (raw)
In-Reply-To: <20240204201657.33079-2-aleksandr.o.makarov@gmail.com> (Aleksandr Makarov's message of "Sun, 4 Feb 2024 22:16:57 +0200")
>>>>> "Aleksandr" == Aleksandr Makarov <aleksandr.o.makarov@gmail.com> writes:
> Setting HAPROXY_CFLAGS on the haproxy build command line overrides CFLAGS
> which were internally set by the haproxy Makefile.
> Among those omitted CFLAGS is -fwrapv. Compiling haproxy without it and
> and then running the program results in runtime error:
> $ haproxy
> FATAL ERROR: invalid code detected -- cannot go further, please recompile!
> ...
> To address this issue, include HAPROXY_CFLAGS in the DEFINE variable instead
> of CFLAGS in haproxy.mk.
> ---
> Changes v1 -> v2
> - Drop patch for haproxy program Makefile, make changes to haproxy.mk instead
Committed to 2023.02.x and 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-02-29 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 20:16 [Buildroot] [PATCH v2] package/haproxy: fix runtime 'FATAL ERROR: invalid code detected -- cannot go further Aleksandr Makarov
2024-02-04 20:16 ` [Buildroot] [PATCH v2] package/haproxy: fix runtime 'FATAL ERROR: invalid code detected -- cannot go further' Aleksandr Makarov
2024-02-05 9:25 ` Yann E. MORIN
2024-02-29 14:21 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edcvic5t.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=aleksandr.o.makarov@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.