On Fri, Mar 21, 2014 at 11:53 AM, CeDeROM wrote:
> Is rebuilding from scratch the only way in this situation? What about
> new dependencies for such package - there will be a conflict between
> my pkg builds and port builds..
OK, I did the portmaster build from ports, VBox works fine and no
other
I have found old package in a pkg cache on another machine. Now I
cannot install it because of unmet dependencies...
Is rebuilding from scratch the only way in this situation? What about
new dependencies for such package - there will be a conflict between
my pkg builds and port builds..
--
CeDeR
Also noticed that since yesterday at least... its not in the "latest" repo..
only in "quarterly" and "release".
Same for other ports like kde... I guess those failed to build.
How often is the latest repo updated? weekly?
Guess the only option for those is build from ports.
Mike
On 20 March 20
On Thu, Mar 20, 2014 at 7:06 PM, Greg Rivers
wrote:
> I found it necessary to `pkg delete compat9x\*`. I don't know why that
> compat package is getting installed.
Ugh, I have uninstalled that package, but before I have tried to
reinstall virtualbox-ose... it seems its gone from repositories!
Da
On Thu, 20 Mar 2014, CeDeROM wrote:
$ VBoxManage
/usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required
by /usr/local/bin/VBoxManage not found
$ VBoxSDL
VBoxSDL: Error -610 in supR3HardenedMainInitRuntime!
VBoxSDL: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed:
/usr/local