From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Benjamin Kamath <kamath.ben@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/lapack: fix build without BUILD_COMPLEX
Date: Sun, 7 Aug 2022 14:42:15 +0200 [thread overview]
Message-ID: <20220807144215.43b7119f@windsurf> (raw)
In-Reply-To: <20220807093135.209053-1-fontaine.fabrice@gmail.com>
On Sun, 7 Aug 2022 11:31:35 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure without BUILD_COMPLEX raised since bump
> to version 3.10.1 in commit b3e96b1fb0d0a7245cea6921fcdd7986762e5ec1 and
> https://github.com/Reference-LAPACK/lapack/commit/bd1fba15d0d6f54891cb822f4ab2e8afd0a3ea4b:
>
> CMake Error at LAPACKE/CMakeLists.txt:38 (message):
> LAPACKE_BUILD_COMPLEX requires BUILD_COMPLEX to be ON
>
> CMake Error at LAPACKE/CMakeLists.txt:38 (message):
> LAPACKE_BUILD_COMPLEX16 requires BUILD_COMPLEX16 to be ON
>
> Fixes:
> - http://autobuild.buildroot.org/results/418d15f734c87a70edf0d670c0548d550e6e70ba
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/lapack/lapack.mk | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-07 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 9:31 [Buildroot] [PATCH 1/1] package/lapack: fix build without BUILD_COMPLEX Fabrice Fontaine
2022-08-07 12:42 ` Thomas Petazzoni via buildroot [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=20220807144215.43b7119f@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=kamath.ben@gmail.com \
--cc=thomas.petazzoni@bootlin.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.