Sorry, i hadn't picked up on this thread at all. What is the concrete patch you
are proposing? Is is in Phabricator somewhere?
(Note that when building with gcc, we should really just automatically add
-latomic, to get rid of these errors.)
-Dimitry
> On 5 Oct 2020, at 05:40, Adrian Chadd wro
On Sun, Oct 4, 2020, 11:07 PM Xin Li wrote:
> Hi,
>
> I'm seeing this panic at boot after upgrading from r366217 to r366364,
> and continues to exist for r366421 (but I haven't find out the exact
> change that caused it). Preloading the relevant kernel modules
> (uhid.ko, ums.ko and wmt.ko) seem
For a couple of weeks now cross-compiling 12-STBALE on CURRENT fails
due to an compiler error in bin/cp/utils.c, see details below.
At this moment, CURRENT is at FreeBSD 13.0-CURRENT #39 r366364: Fri Oct
2 17:51:39 CEST 2020 amd64 and the sources for 12-STABLE are at
revision 366437.
The compila
ping!
I've got the world building on gcc + mips32 just patching cxx_contention_t
to be 32 bits, but it looks like an ABI change.
Would the better thing be to just make it 32 bits on FreeBSD + MIPS for
now? I don't think anyone is going to mind that changing at this point.
-adrian
On Sat, 3 O
I just tried to boot FreeBSD 12.1-RC1 in KVM/QEMU. Specifically, I booted
FreeBSD-12.2-RC1-amd64-memstick.img as a virtual USB HDD. The console was
flooded with error messages about "Device not configured"and errors from
the rc scripts, then it hanged. Screenshot linked. Any ideas?
http://bayi
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
