Ok, no problem. Just wanted to confirm that you were no longer working on it. Thanks so much for all the work you've done over the years to support it. Hope whatever you're doing now is rewarding and that you come through the current craziness in good shape. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Mon, Mar 23, 2020 at 11:48 AM Jung-uk Kim <j...@freebsd.org> wrote: > On 20. 3. 23., Kevin Oberman wrote: > > vbox@ was folded into emulators@ a long time ago, shortly after the port > > stabilized about a decade ago. jkim@ has been supporting it and is > > effectively the maintainer and had done an outstanding job. The problem > is > > that I have not seen anything from him in several months. The result is > > little going on. Kyle made the commit about this issue and that appears > to > > be the only commit since jkim's commit to the kmod last October. > > I am sorry but I am not doing much about VirtualBox because I am rarely > using it nowadays. > > Jung-uk Kim > > > Can someone in emulators comment? > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > E-mail: rkober...@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > > > > On Mon, Mar 23, 2020 at 1:47 AM Gerald Pfeifer <ger...@pfeifer.com> > wrote: > > > >> On Sun, 22 Mar 2020, Kyle Evans wrote: > >>>> Okay to change this to USE_GCC=yes? > >>> It's actually needing to be changed back away from GCC, because this > >>> inherently breaks as the qt bits it uses are compiled with llvm and > >>> used an incompatible libc++ -- there's an open PR about it after this > >>> commit, I'm trying to work out where newer clang is failing to compile > >>> properly. =-( > >> > >> Hopefully Piotr's suggestion helps? > >> > >> (I'll refrain from touching this then.) > >> > >>> I seem to recall the situation is that there's now an effectively > >>> one-man vbox@ team, and this seems to be mostly on life-support. > >> > >> In fact, in response to my mail I got a note from emulators@ that > >> the message was sent to a closed list, so looks as if vbox@ is now > >> redirecting there? A little confusing... > _______________________________________________ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
