From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tril <tril@metapipe.net>
Cc: 60082-done@debbugs.gnu.org
Subject: bug#60082: openblas FTBFS in KVM with default CPU
Date: Sat, 09 Mar 2024 20:02:33 -0500 [thread overview]
Message-ID: <87v85udhli.fsf@gmail.com> (raw)
In-Reply-To: <20221214172435.GB1182@bespin.org> (tril@metapipe.net's message of "Wed, 14 Dec 2022 09:24:35 -0800")
Hi,
<tril@metapipe.net> writes:
> FTBFS = "Fails To Build From Source"
>
> guix package --no-substitutes -i openblas
>
> resulted in the error below on Guix System running on a KVM in Proxmox
> VE using the default CPU called "kvm64".
>
> ---
> OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./sblat3 < ./sblat3.dat
>
> Program received signal SIGILL: Illegal instruction.
>
> Backtrace for this error:
> #0 0x7ffff7d2fc1a
> #1 0x7ffff7d2ee45
> #2 0x7ffff7a2209f
> #3 0x186ac04
> bash: line 1: 25848 Illegal instruction OPENBLAS_NUM_THREADS=1
> OMP_NUM_THREADS=1 ./sblat3 < ./sblat3.dat
>
> make[1]: *** [Makefile:167: level3] Error 132
> ---
>
> I shutdown the VM and changed the CPU type to "host" (which provides the full
> instruction set of my CPU to the VM) and was able to build successfully
> using the same command.
>
> openblas 0.3.20 out
> /gnu/store/xghpgl3fnr603z16vg7hldmpxygriqm2-openblas-0.3.20
Thanks for the report. That's probably due to some limitation in QEMU.
It'd be best to report it there -- it's outside of the scope of Guix,
although you could offer a Guix-based reproducer in your upstream
report.
Closing.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-03-10 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 17:24 bug#60082: openblas FTBFS in KVM with default CPU Tril
2024-03-10 1:02 ` Maxim Cournoyer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v85udhli.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=60082-done@debbugs.gnu.org \
--cc=tril@metapipe.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).