Date: Sun, 26 Apr 2015 11:21:50 -0400 From: Michael Butler <imb@protected-networks.net> To: Kevin Oberman <rkoberman@gmail.com> Cc: "freebsd-emulation@freebsd.org" <emulation@freebsd.org> Subject: Re: Unable to build virtualbox-ose after latest round up updates Message-ID: <553D028E.1020100@protected-networks.net> In-Reply-To: <CAN6yY1seE0ErMbY9ataveZi3Q685C7cHXN0GqRit4Q2PsFCMGg@mail.gmail.com> References: <CAN6yY1u1QsHTzjYFUcv9QJ1txtK5Hbi8X09AFOHSJk2voHWw2Q@mail.gmail.com> <553C421E.1060108@protected-networks.net> <CAN6yY1seE0ErMbY9ataveZi3Q685C7cHXN0GqRit4Q2PsFCMGg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/26/15 00:02, Kevin Oberman wrote: > On Sat, Apr 25, 2015 at 6:40 PM, michael butler > > Any idea how to deal with this? Is anyone else seeing this? > > Running 10-Stable r281259 with almost all ports up to date > except chromium > (which should have nothing to do with this issue). > > I really need to get my Windows 7 VM running again. > > I ran into something similar with KDE (still dealing with that :-() > but the situation was improved somewhat by recompiling qt4-core, > > imb > > > Michael, > > Thanks so much! That did the trick, though I am at a loss as to why. I > rebuilt qt4-corelib and just finished a successful build of VB. With or about the time of the ICU update, there was apparently a change in name-mangling for one symbol related to libgthread. This seemed to cause all manner of mysterious failures. I'm glad that worked, I haven't made it that far yet; Too much time on aircraft and too little on maintenance :-( imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553D028E.1020100>