From: Christopher Baines <mail@cbaines.net>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, 56353@debbugs.gnu.org
Subject: bug#56353: sbcl-2.2.6 build fail
Date: Sat, 02 Jul 2022 20:26:40 +0100 [thread overview]
Message-ID: <87edz36zm5.fsf@cbaines.net> (raw)
In-Reply-To: <87o7y74eid.fsf@kitej>
[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]
Guillaume Le Vaillant <glv@posteo.net> writes:
> [[PGP Signed Part:Undecided]]
> 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?
Sure, here is the lscpu output from the bayfront and harbourfront
machines.
[-- Attachment #1.2: bayfront lscpu output --]
[-- Type: text/plain, Size: 2303 bytes --]
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 Opteron(tm) Processor 6278
CPU family: 21
Model: 1
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 2
Stepping: 2
Frequency boost: enabled
CPU max MHz: 2400.0000
CPU min MHz: 1400.0000
BogoMIPS: 4799.96
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 amd_dcm aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legac
y abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 topoext perfctr_core perfctr_nb cpb hw_pstate ssbd vmmcall arat npt lbrv svm_lock nrip_save ts
c_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 512 KiB (32 instances)
L1i: 1 MiB (16 instances)
L2: 32 MiB (16 instances)
L3: 24 MiB (4 instances)
NUMA:
NUMA node(s): 4
NUMA node0 CPU(s): 0-7
NUMA node1 CPU(s): 8-15
NUMA node2 CPU(s): 16-23
NUMA node3 CPU(s): 24-31
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Full AMD retpoline, STIBP disabled, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
[-- Attachment #1.3: harbourfront lscpu --]
[-- Type: text/plain, Size: 1685 bytes --]
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 38 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz
CPU family: 6
Model: 23
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 2
Stepping: 10
BogoMIPS: 4987.55
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts
rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm pti dtherm
Caches (sum of all):
L1d: 256 KiB (8 instances)
L1i: 256 KiB (8 instances)
L2: 24 MiB (4 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-7
Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX unsupported
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Meltdown: Mitigation; PTI
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Full generic retpoline, STIBP disabled, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2022-07-02 20:15 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
2022-07-02 19:26 ` Christopher Baines [this message]
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=87edz36zm5.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=56353@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=me@tobias.gr \
/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).