Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread Mark Millard
Warner Losh wrote on Date: Thu, 30 Mar 2023 22:15:38 UTC : > On Thu, Mar 30, 2023, 3:45 PM void wrote: > > > On Thu, Mar 30, 2023 at 12:56:53PM -0700, Mark Millard wrote: > > > > >To my knowledge, FreeBSD has not actively supported newer > > >FreeBSD building older FreeBSD across versions. > >

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread Warner Losh
On Thu, Mar 30, 2023, 3:45 PM void wrote: > On Thu, Mar 30, 2023 at 12:56:53PM -0700, Mark Millard wrote: > > >To my knowledge, FreeBSD has not actively supported newer > >FreeBSD building older FreeBSD across versions. > > Are you sure? I routinely build & run 12.4 and 12-stable bhyve and > poud

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread void
On Thu, Mar 30, 2023 at 12:56:53PM -0700, Mark Millard wrote: To my knowledge, FreeBSD has not actively supported newer FreeBSD building older FreeBSD across versions. Are you sure? I routinely build & run 12.4 and 12-stable bhyve and poudriere jail instances on -current. --

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread Mark Millard
Mateusz Guzik wrote on Date: Thu, 30 Mar 2023 14:56:09 UTC : > On 3/30/23, Mateusz Guzik wrote: > > On 3/30/23, FreeBSD User wrote: > >> . . . > > > > So I looked into it and landed > https://cgit.FreeBSD.org/src/commit/?id=82eb549f800e08158802b74bef62e7db0939a3fe > > As of that commit I can

Re: Kernel panic on jail start

2023-03-30 Thread Dmitry Chagin
On Thu, Mar 30, 2023 at 07:08:28PM +0200, Goran Mekić wrote: > Hello, > > I get the kernel panic when starting jail. With git bisect I found out > the offending commit is 0b56641cfcda30d06243223f37781ccc18455bef. After > reverting it, everything is back to normal. For completeness, this is my > ja

Kernel panic on jail start

2023-03-30 Thread Goran Mekić
Hello, I get the kernel panic when starting jail. With git bisect I found out the offending commit is 0b56641cfcda30d06243223f37781ccc18455bef. After reverting it, everything is back to normal. For completeness, this is my jail.conf: network { $id = 1; $base = /var/jails; persist; vnet;

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread FreeBSD User
Am Thu, 30 Mar 2023 17:27:31 +0200 Dag-Erling Smørgrav schrieb: > FreeBSD User writes: > > I tried to put the option > > > > WITHOUT_MODULE="an" > > it's spelled WITHOUT_MODULES, cf. make.conf(5). > > DES Correct, and so I use it ... ;-) [...] # BUILD and INSTALL! # Options to put in make

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread Dag-Erling Smørgrav
FreeBSD User writes: > I tried to put the option > > WITHOUT_MODULE="an" it's spelled WITHOUT_MODULES, cf. make.conf(5). DES -- Dag-Erling Smørgrav - d...@freebsd.org

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread FreeBSD User
Am Thu, 30 Mar 2023 15:53:19 +0200 Mateusz Guzik schrieb: > On 3/30/23, FreeBSD User wrote: > > Hello folks, > > > > some strange misbehaviour in a NanoBSD compilation is driving me nuts. > > Recently I posted some > > error messages regarding > > > > [...] > > src/sys/dev/an/if_an_pci.c:143:1:

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread FreeBSD User
Am Thu, 30 Mar 2023 16:56:09 +0200 Mateusz Guzik schrieb: > On 3/30/23, Mateusz Guzik wrote: > > On 3/30/23, FreeBSD User wrote: > >> Hello folks, > >> > >> some strange misbehaviour in a NanoBSD compilation is driving me nuts. > >> Recently I posted some > >> error messages regarding > >> >

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread Mateusz Guzik
On 3/30/23, Mateusz Guzik wrote: > On 3/30/23, FreeBSD User wrote: >> Hello folks, >> >> some strange misbehaviour in a NanoBSD compilation is driving me nuts. >> Recently I posted some >> error messages regarding >> >> [...] >> src/sys/dev/an/if_an_pci.c:143:1: error: a >> function definition wi

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread Mateusz Guzik
On 3/30/23, FreeBSD User wrote: > Hello folks, > > some strange misbehaviour in a NanoBSD compilation is driving me nuts. > Recently I posted some > error messages regarding > > [...] > src/sys/dev/an/if_an_pci.c:143:1: error: a > function definition without a prototype is deprecated in all versio

NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

2023-03-30 Thread FreeBSD User
Hello folks, some strange misbehaviour in a NanoBSD compilation is driving me nuts. Recently I posted some error messages regarding [...] src/sys/dev/an/if_an_pci.c:143:1: error: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Werror,-

x11/libinput assertion error

2023-03-30 Thread Charlie Li
Somewhere between -CURRENT 0e71f4f77c016b4087106e7c58b958667df8e1b2 and a02d9cad77c1207eb809ba49fc1595c8ebb2da26, xorg-server crashes on launch. It happens right when loading xf86-input-libinput, for which the error only mentions a segfault at 0x0b. Switching to xf86-input-evdev (and removing x