Re: Error crosscompiling 14.0-ALPHA1 on amd64 for arm64.aarch64

Mike Karels wrote on Date: Sat, 12 Aug 2023 22:17:39 UTC : On 12 Aug 2023, at 15:32, Juraj Lutter wrote: > > Hi, > > > > recent 14.0-ALPHA1 sources is giving an error: > > > > Building > > /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libssp_nonshared/libssp_nonshared.o > > Building

RE: Error crosscompiling 14.0-ALPHA1 on amd64 for arm64.aarch64

Juraj Lutter wrote on Date: Sat, 12 Aug 2023 20:32:53 UTC : > recent 14.0-ALPHA1 sources is giving an error: > > Building > /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libssp_nonshared/libssp_nonshared.o > Building /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libgcc_eh/int_util.o > error:

Re: Error crosscompiling 14.0-ALPHA1 on amd64 for arm64.aarch64

On 12 Aug 2023, at 15:32, Juraj Lutter wrote: > Hi, > > recent 14.0-ALPHA1 sources is giving an error: > > Building > /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libssp_nonshared/libssp_nonshared.o > Building /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libgcc_eh/int_util.o > error: unable to

Error crosscompiling 14.0-ALPHA1 on amd64 for arm64.aarch64

Hi, recent 14.0-ALPHA1 sources is giving an error: Building /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libssp_nonshared/libssp_nonshared.o Building /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libgcc_eh/int_util.o error: unable to create target: 'No available targets are compatible with

14.0-APLHA1 snapshot use of kyua: An odd backtrace that appeared on the aarch64 console (and logs)

I ran the block of zfs tests on a snapshot 14.0-APLHA1 install used to boot and operate a Windows Dev Ket 2023. I just noticed a non-panic/non-crash backtrace had been output to the console (and related logs): . . . GEOM: md0: the primary GPT table is corrupt or invalid. GEOM: md0: using the

Re: ZFS deadlock in 14

On August 12, 2023 7:11:10 AM PDT, "Dag-Erling Smørgrav" wrote: >Dag-Erling Smørgrav writes: >> At some point between 42d088299c (4 May) and f0c9703301 (26 June), a >> deadlock was introduced in ZFS. > >Trying to narrow this range down, I did not get a deadlock with >4e8d558c9d1c (10 June) but

Re: [Intel AlderLake] Read files to FAT32 or UFS partition cause data corrupt due to P-Core-Core

On Tue, Aug 8, 2023 at 10:50 AM Michael Butler wrote: > On 8/8/23 10:56, Tomoaki AOKI wrote: > > On Tue, 8 Aug 2023 17:02:32 +0300 > > Konstantin Belousov wrote: > > [ .. snip .. ] > > >> The workaround is switched on automatically, when kernel detects 'small > cores' > >> reported by CPUID.

Re: periodic daily produces ridiculously huge report files

Michael Grimm wrote > Ever since either upgrading to MAIN or WITHOUT_INET6=yes [1] I noticed that > periodic daily still runs in the morning failing to mail ridiculously huge > report files (>= 90 *GB*). > > [1] Can't remember when this started. FTR: It started with WITHOUT_INET6=yes.

Re: ZFS deadlock in 14

Dag-Erling Smørgrav writes: > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > deadlock was introduced in ZFS. Trying to narrow this range down, I did not get a deadlock with 4e8d558c9d1c (10 June) but I did with b7198dcfc039 (16 June), albeit after building ~1800 packages.

Re: lang/gcc12 will not build on a host w/ 8 CPU and 16G mem

El día sábado, agosto 12, 2023 a las 01:38:32p. m. +, Lorenzo Salvadore escribió: > Hello, I am the port maintainer. > > It is a well known issue unfortunately. Just disable the LTO_BOOTSTRAP option > and the build will succeed. > > Cheers, > > Lorenzo Salvadore Lorenzo, Thanks for this

Re: lang/gcc12 will not build on a host w/ 8 CPU and 16G mem

Hello, I am the port maintainer. It is a well known issue unfortunately. Just disable the LTO_BOOTSTRAP option and the build will succeed. Cheers, Lorenzo Salvadore Sent from Proton Mail mobile Messaggio originale Il 12 Ago 2023, 15:33, Matthias Apitz ha scritto: > I'm

lang/gcc12 will not build on a host w/ 8 CPU and 16G mem

I'm building on 14-CURRENT with poudriere. The server in question is a Dell R210 with 8x 3.30GHz CPU and 15.8 GB memory: Aug 11 19:03:21 jet kernel: CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz (3292.74-MHz K8-class CPU) Aug 11 19:03:21 jet kernel: FreeBSD/SMP: Multiprocessor System Detected:

Re: problem with poudriere && port ftp/curl

El día viernes, agosto 11, 2023 a las 11:59:45p. m. +0200, Jan Beich escribió: > Matthias Apitz writes: > > > I have the following problem with poudriere on 14-CURRENT and ports from > > git head: every time when I start poudriere-bulk it removes a port > > already compile fine (and all its

Re: ssh 9.4 fails to build

On Sat, 12 Aug 2023 08:04:29 +0200 (CEST) Ronald Klop wrote: > Hi, > > I get this error while building world. > NB: I'm building with llvm15 from a pkg. But I don't think that should make a > difference. > ld.lld: error: undefined symbol: Fssh_lib_contains_symbol > >>> referenced by

Re: aarch64 (not armv7) kyua run on main [so: 14]: sys/net/if_lagg_test:status_stress got "Fatal data abort" panic [14.0-ALPHA1 snapshot panic submitted to bugzilla]

On Aug 9, 2023, at 22:30, Mark Millard wrote: > The context is on a Windows Dev Kit 2023, using a bectl based boot/root disk: > > # uname -apKU > FreeBSD CA78C-WDK23-ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT aarch64 1400094 #9 > main-n264643-0befc55cdf4b-dirty: Wed Aug 9 14:23:48 PDT 2023 >

ssh 9.4 fails to build

Hi, I get this error while building world. NB: I'm building with llvm15 from a pkg. But I don't think that should make a difference. ld.lld: error: undefined symbol: Fssh_lib_contains_symbol referenced by ssh-pkcs11.c:1538 (/usr/src/crypto/openssh/ssh-pkcs11.c:1538)