Am 04.05.2014 20:44 schrieb "Melvyn Sopacua" <mel...@magemana.nl>: > > Hi, > > emulators/virtualbox-ose-additions always fails for me in the stage > installation, so today I looked a bit further: > > Bad: > install -o root -g wheel -m 444 > /usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_.so > /usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so > > Good: > install -o root -g wheel -m 444 > /usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_17.so > /usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so > > The difference between bad and good are the 17 missing in the shared > object name. The bad line is created in a clean build and the good line > if one invokes the install target immediately after that failed one. > > Is make really loosing a variable here or could this be a parallelization issue in the upstream build system?
That command is part of the port makefile so it's for sure not an upstream bug. Sounds like the xserver version that is used there is not read properly in some case. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
