https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878
--- Comment #89 from Mario Lobo ---
I agree with you completely, but we are lagging so far behind on the hosting
side (ose and ose-kmod) that I think people that are trying to upgrade it
aren't even thinking about the guest-additions port.
Quoting "Mikhail T." (from Fri, 19 Jun 2020
14:59:35 -0400):
On 19.06.20 04:52, Tijl Coosemans wrote:
You should not use USE_LINUX_RPM. It's meant for infrastructure ports.
Yes, this is the current stance, but it seems like an unnecessary
limitation... :( Software distributed by vendors i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878
--- Comment #90 from Mario Lobo ---
For the record:
FreeBSD 13.0-CURRENT #1 r360882
Managed to compile cleanly virtualbox-ose-6.1.10 and
virtualbox-ose-kmod-6.1.10.
Modules load OK:
kldstat | grep vbox
43 0x8122c0008cba8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234878
--- Comment #91 from Mario Lobo ---
A small correction.
Starting the VM with VBoxHeadless or VBoxSDL, it just hangs open on the
terminal, the process doesn't end with ^C, and even if the terminal is closed,
the process still hangs in there
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247430
--- Comment #2 from Mikhail Teterin ---
> I don't object to adding a knob for this somewhere, perhaps via
> bsd.default-versions.mk since this would be a tree-wide option and not a
> per-port option.
Actually, it might still be per-port,
Gentlemen!
An old bug in the patch is causing compiler-warnings, and leads to
erroneous behavior where pointers are bigger than 32-bit.
Moreover, given the memcpy right after it, the bzero is simply not
needed at all. Instead of removing the bogus ampersand, the entire line
should be deleted
