From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcorrect: fix debug build
Date: Mon, 19 Nov 2018 21:42:01 +0100 [thread overview]
Message-ID: <20181119214201.185c2e54@windsurf.home> (raw)
In-Reply-To: <20181119174629.1613-1-fontaine.fabrice@gmail.com>
Hello,
On Mon, 19 Nov 2018 18:46:29 +0100, Fabrice Fontaine wrote:
> If BR2_ENABLE_DEBUG is set, Debug release will be used and as a result
> -fsanitize=address will be added to CFLAGS which will fail on some
> toolchains because it requires asan library
>
> So add -DCMAKE_BUILD_TYPE=Release unconditionally
>
> Fixes:
> - http://autobuild.buildroot.net/results/221d6a418e75b39fe645c3a56cee676518d2cff6
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libcorrect/libcorrect.mk | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/libcorrect/libcorrect.mk b/package/libcorrect/libcorrect.mk
> index 0a84aa5c26..cb25e0d0cd 100644
> --- a/package/libcorrect/libcorrect.mk
> +++ b/package/libcorrect/libcorrect.mk
> @@ -9,5 +9,7 @@ LIBCORRECT_SITE = $(call github,quiet,libcorrect,$(LIBCORRECT_VERSION))
> LIBCORRECT_LICENSE = BSD-3-Clause
> LIBCORRECT_LICENSE_FILES = LICENSE
> LIBCORRECT_INSTALL_STAGING = YES
> +# Debug release adds -fsanitize=address so always use Release
> +LIBCORRECT_CONF_OPTS = -DCMAKE_BUILD_TYPE=Release
This is a bit of a hack. What about making upstream check if
-fsanitize=address is supported by the toolchain before using it ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-11-19 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 17:46 [Buildroot] [PATCH 1/1] libcorrect: fix debug build Fabrice Fontaine
2018-11-19 20:42 ` Thomas Petazzoni [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=20181119214201.185c2e54@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox