From: Guillaume Le Vaillant <glv@posteo.net>
To: Christopher Baines <mail@cbaines.net>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>,
xiewensheng@hotmail.com, 56353@debbugs.gnu.org
Subject: bug#56353: sbcl-2.2.6 build fail
Date: Sat, 02 Jul 2022 17:08:53 +0000 [thread overview]
Message-ID: <87o7y74eid.fsf@kitej> (raw)
In-Reply-To: <87ilof78y0.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 4092 bytes --]
Christopher Baines <mail@cbaines.net> skribis:
> Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
>
>> On 2 July 2022 09:29:22 UTC, Wensheng Xie <xiewensheng@hotmail.com> wrote:
>>>Das Erstellungsprotokoll kann unter „/var/log/guix/drvs/6l/q7dfdfzrlp24lmhj95fcnvkr2mrqfz-sbcl-2.2.6.drv.bz2“ eingesehen werden.
>>
>>
>> This log file is always a good idea to include.
>
> I think this is the equivalent non-grafted derivation:
>
> https://data.guix.gnu.org/gnu/store/m7xw777v5agldb76gbqkqdvrrlj5d7zy-sbcl-2.2.6.drv
>
> There are plenty of failed builds on bordeaux.guix.gnu.org. I managed to
> get it to build successfully once though on my laptop.
>
> Guillaume, any ideas if sbcl@2.2.6 is just really unlikely to build
> successfully, or if there's particular conditions for it to build?
>
> Thanks,
>
> Chris
According to the logs, the 'build-doc' phase fails to compile the
documentation for SIMD related functions. There's a patch disabling this
part of the doc unless we compile on x86_64, but maybe not all x86_64
CPUs have the required instructions...
Would it be possible to get the result of "lscpu" on some machines where
it fails?
The build always works on my machine:
--8<---------------cut here---------------start------------->8---
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 48 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 32
On-line CPU(s) list: 0-31
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 9 5950X 16-Core Processor
CPU family: 25
Model: 33
Thread(s) per core: 2
Core(s) per socket: 16
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU max MHz: 5083.3979
CPU min MHz: 2200.0000
BogoMIPS: 6786.83
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_go
od nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy sv
m extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate
ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc c
qm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists paus
efilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 512 KiB (16 instances)
L1i: 512 KiB (16 instances)
L2: 8 MiB (16 instances)
L3: 64 MiB (2 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-31
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP always-on, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
--8<---------------cut here---------------end--------------->8---
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-07-02 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 9:29 bug#56353: sbcl-2.2.6 build fail Wensheng Xie
2022-07-02 11:40 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-07-02 16:49 ` Christopher Baines
2022-07-02 17:08 ` Guillaume Le Vaillant [this message]
2022-07-02 19:26 ` Christopher Baines
2022-07-03 8:33 ` bokr
2022-07-03 8:51 ` Guillaume Le Vaillant
2022-07-03 10:09 ` Guillaume Le Vaillant
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=87o7y74eid.fsf@kitej \
--to=glv@posteo.net \
--cc=56353@debbugs.gnu.org \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
--cc=xiewensheng@hotmail.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.
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).