Re: [Call For Testing] VirtualBox for FreeBSD! take 4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -END PGP SIGNATURE- ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Hi Martin Many thanks again ! One more question, what about USB support ? Is it possible to pass host usb devices inside VM ? I have such option in machine menu but it is always empty. $ usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: UHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: EHCI root HUB Intel at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen4.2: product 0x4486 IBM at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.3: Microsoft 5-Button Mouse with IntelliEye(TM) Microsoft at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.2: BCM2045B Broadcom Corp at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.3: Biometric Coprocessor STMicroelectronics at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON $ As minimum ugen3.3 have no driver attached. Also I have RW permissions to access /dev/usb* devices. -Original Message- From: Martin Wilke m...@freebsd.org To: po...@freebsd.org Cc: freebsd-emulat...@freebsd.org, freebsd-curr...@freebsd.org Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 Date: Wed, 27 May 2009 15:43:43 +0200 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -END PGP SIGNATURE- ___ freebsd-emulat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org -- Vladimir B. Grebenschikov v...@fbsd.ru ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Rink Springer wrote: On Wed, May 27, 2009 at 06:50:20PM +0400, Vladimir Grebenschikov wrote: One more question, what about USB support ? Is it possible to pass host usb devices inside VM ? I think this is only possible with the non-open-source version of VirtualBox. Regards, Maybe Sun/Innotek has some spare time and makes an official Release. I See it coming :) - A Windows VM just for Webcam stuff... Maybe the new USB-Stack and libusb makes Support on the VBox side really easy. best regards ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
On Wed, May 27, 2009 at 4:43 PM, Martin Wilke m...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) Hi Martin, I'm running RELENG_7, I've just given it a spin, I was able to install another FreeBSD instance in the virtual machine. Working great! Any idea when this will hit the ports tree? As a side note, loading vboxdrv.ko while X was running crashed my machine, in RTMpGetOnlineCount (). Unfortunately, all frames between that and frame 0 were corrupt. After rebooting, I was able to log on ttyv0 and loaded it without any issues. ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Martin Wilke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ |Mess with the Best, Die like the Rest!| +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -END PGP SIGNATURE- ___ 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 --- Fletcher Moorland Limited is a company registered in England and Wales. Registration number: 2984467. Registered office: Elenora Street, Stoke on Trent, Staffordshire, ST4 1QG. VAT Registration number: 478730606 Telephone: 01782 411021 | Fax: 01782 744470 | http://www.fletchermoorland.co.uk Hi, With both VirtualBox 4 and 5, when I try to run VirtualBox I get an error saying Callee RC: NS_ERROR_ABORT (0x80004004) If I run VBoxSVC is a console session and then try VirtualBox I get ** Sun VirtualBox XPCOM Server Version 2.2.51_OSE (C) 2008-2009 Sun Microsystems, Inc. All rights reserved. Starting event loop [press Ctrl-C to quit] terminate called after throwing an instance of 'settings::ENoValue' what(): Segmentation fault: 11 (core dumped) Also, when I try to compile VirtualBox 5 with debug information, the make fails with kBuild: Linking tstDir In file included from /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:47: /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/../SUPDrvInternal.h:125:1: warning: ffs redefined In file included from /usr/src/sys/sys/systm.h:42, from /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:40: /usr/include/machine/cpufunc.h:133:1: warning: this is the location of the previous definition kBuild: Linking tstDir-2 kBuild: Linking tstDir-3 /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary kmk[2]: *** [/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 The failing command: @gcc -c -g -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 -fno-stack-protector -O0 -fno-omit-frame-pointer -nostdinc -std=c99 -m64 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -Wundef -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include -I/usr/include -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/include -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\/usr/local/lib/virtualbox\
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Paul Wootton wrote: Martin Wilke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ |Mess with the Best, Die like the Rest!| +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -END PGP SIGNATURE- ___ 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 --- Fletcher Moorland Limited is a company registered in England and Wales. Registration number: 2984467. Registered office: Elenora Street, Stoke on Trent, Staffordshire, ST4 1QG. VAT Registration number: 478730606 Telephone: 01782 411021 | Fax: 01782 744470 | http://www.fletchermoorland.co.uk Hi, With both VirtualBox 4 and 5, when I try to run VirtualBox I get an error saying Callee RC: NS_ERROR_ABORT (0x80004004) If I run VBoxSVC is a console session and then try VirtualBox I get ** Sun VirtualBox XPCOM Server Version 2.2.51_OSE (C) 2008-2009 Sun Microsystems, Inc. All rights reserved. Starting event loop [press Ctrl-C to quit] terminate called after throwing an instance of 'settings::ENoValue' what(): Segmentation fault: 11 (core dumped) Also, when I try to compile VirtualBox 5 with debug information, the make fails with kBuild: Linking tstDir In file included from /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:47: /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/../SUPDrvInternal.h:125:1: warning: ffs redefined In file included from /usr/src/sys/sys/systm.h:42, from /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:40: /usr/include/machine/cpufunc.h:133:1: warning: this is the location of the previous definition kBuild: Linking tstDir-2 kBuild: Linking tstDir-3 /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary kmk[2]: *** [/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 The failing command: @gcc -c -g -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 -fno-stack-protector -O0 -fno-omit-frame-pointer -nostdinc -std=c99 -m64 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -Wundef -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include -I/usr/include -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/include -I/root/vBox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Vlad GALU wrote: As a side note, loading vboxdrv.ko while X was running crashed my machine, in RTMpGetOnlineCount (). Unfortunately, all frames between that and frame 0 were corrupt. After rebooting, I was able to log on ttyv0 and loaded it without any issues. Regarding my previous message about loading vboxdrv causing my machine to wedge, it happens to me both in X and on the console. Haven't tried with v5 of the port yet though. Doug ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
2009/5/27 Martin Wilke m...@freebsd.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) I can't make install WITH_GUESTADDITIONS=yes if I don't download the iso manually into /usr/ports/distfiles/ : # make install [...] install -o root -g wheel -m 444 /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso /usr/local/lib/virtualbox/ install: /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso: No such file or directory *** Error code 71 Also, are there any plans on VT and x86_64 guests support (blocking feature for me) ? Thanks for the great port ! Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +---+---+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -END PGP SIGNATURE- ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email vCards X www: http://www.gid0.org- against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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
pkg_add errors
During my last run of 'pkg_upgrade -a', cups-client forgot to install the library libcups.so.2, which I fortunately recognized due to my routine of running pkg_libchk after every package/port upgrade. Running 'pkg_upgrade cups-client' fixed that problem. The interesting part is, that the reinstallation of cups-client was done from the same package. So either pkg_add, tar or the file system were to blame, because the package is without fault. I expect that this unreliability of pkg_add (or the underlying systems) has a severe impact on my further development of pkg_upgrade. A simple check whether the package has been fully installed using 'pkg_info -g' is not a solution, because many packages (e.g. scribus or gstreamer-plugins-bad) come with faulty PLISTs, so 'pkg_info -g' is not a reliable way to check for a successful install. Maintainers have successfully ignored my bitching about broken PLISTs for years, so I cannot expect this to be solved upstream. The problem I face is that there are cases when a package installs incompletely. I can detect this and attempt a reinstall or even a redownload and reinstall. But what if the install is still broken? Terminate pkg_upgrade with an error? That does not look like an option to me, because it would quit whenever a package with a broken PLIST is encountered and rendered almost useless by this. At least for as long as committers accept ports with broken PLISTs. What I need is a solution that is right most of the time, does not cause pkg_upgrade to stop and can be easily redeemed afterwards, if it hasn't been right after all. I have found such a solution for the conflict handling (existing packages take preference, so e.g. boost-python will be accepted as a dependency instead of boost, or a2ps-a4 instead of a2ps-letter). If the default solution was wrong the packages can easily be exchanged using -o or -C. I need something similar for the incomplete package problem. Should pkg_upgrade create a summary of apparently broken packages that have been installed? Should it bail out (and break with every package that has a broken plist)? Should it perform library checks and try to auto fix them? My preference would be to rely on 'pkg_info -g', but that would require all committers to run extensive checks before committing changes to the ports tree. Miwi has always done this and more than once revealed PLIST problems of my ports to me. But I wonder whether it is really sensible to ask committers to test everything on a Tinderbox (preferably on several platforms) before committing changes to the ports tree. ___ 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
Re: MAKE_JOBS_UNSAFE (some more ports)
On Tuesday 26 May 2009 23:23:16 Pav Lucistnik wrote:
David Naylor píše v út 26. 05. 2009 v 18:17 +0200:
What about the change that exposes MAKE_JOBS_NUMBER when MAKE_JOBS_SAFE
or FORCE_MAKE_JOBS are defined (to avoid using ${_MAKE_JOBS:C/-j//}, not
sure what the policy is of ports using *.mk internals). I think that is
a reasonable change???
I think it's reasonable. It will need to be tested widely. Can you file
a PR with just that change, to help me track it while in testing?
Done, please see PR ports/134977. This should not have any functional change
and the only ports (at this stage) that will use MAKE_JOBS_NUMBER is OOo*
(although games/teeworld is the next closest candidate).
I've also made some changes to how OOo2 handles concurrency, as pav@ pointed
out `make -j1` is different to `make` and OOo2 now differentiates between the
two, could someone please check if the following work:
(cd /usr/ports/editors/openoffice.org-2; make MAKE_JOBS_NUMBER=1)
OOo3 should be functionally the same to the previous patch however it does not
make the distinction between `make -j1` and `make` and I don't know enough
about the build process to know how to add a normal `make`.
Thanks for all your patience.
David
P.S. This should have been sent ~9 hours ago, but internet went down.
P.P.S. This should be the final patch (pending OOo2 verification).
diff -ur /usr/ports/Mk/bsd.port.mk ports/Mk/bsd.port.mk
--- /usr/ports/Mk/bsd.port.mk 2009-05-23 13:20:58.0 +0200
+++ ports/Mk/bsd.port.mk 2009-05-27 08:38:44.0 +0200
@@ -2185,11 +2185,8 @@
_MAKE_JOBS= #
.else
.if defined(MAKE_JOBS_SAFE) || defined(FORCE_MAKE_JOBS)
-.if defined(MAKE_JOBS_NUMBER)
+MAKE_JOBS_NUMBER?= `${SYSCTL} -n kern.smp.cpus`
_MAKE_JOBS= -j${MAKE_JOBS_NUMBER}
-.else
-_MAKE_JOBS= -j`${SYSCTL} -n kern.smp.cpus`
-.endif
.if defined(FORCE_MAKE_JOBS)
BUILD_FAIL_MESSAGE+= You have chosen to use multiple make jobs (parallelization) for all ports. This port was not tested for this setting. Please remove FORCE_MAKE_JOBS and retry the build before reporting the failure to the maintainer.
.endif
diff -ur /usr/ports/editors/openoffice.org-2/Makefile ports/editors/openoffice.org-2/Makefile
--- /usr/ports/editors/openoffice.org-2/Makefile 2009-01-25 10:45:45.0 +0200
+++ ports/editors/openoffice.org-2/Makefile 2009-05-27 08:38:27.0 +0200
@@ -51,6 +51,7 @@
USE_PERL5= yes
USE_BZIP2= yes
WITHOUT_CPU_CFLAGS= true
+MAKE_JOBS_SAFE= yes
.include bsd.port.pre.mk
@@ -132,7 +133,6 @@
CONFIGURE_WRKSRC= ${WRKSRC}/config_office
TCSH?= /bin/tcsh
PKGMESSAGE= ${WRKDIR}/pkg-message
-NUMOFPROCESSES?= 1
CONFIGURE_ARGS+= --with-gnu-cp=${LOCALBASE}/bin/gcp \
--with-gnu-patch=${LOCALBASE}/bin/gpatch \
@@ -192,8 +192,8 @@
do-build:
@cd ${WRKSRC} ; ./bootstrap
# PR:84786 #i53289#
-.if (${NUMOFPROCESSES}1)
- @cd ${WRKSRC} ; ${SETENV} LANG=C LC_ALL=C ${TCSH} -c source ${FREEBSD_ENV_SET} ; setenv TMP ${WRKSRC} ; cd instsetoo_native ; build.pl -P${NUMOFPROCESSES} --all
+.if !defined(DISABLE_MAKE_JOBS)
+ @cd ${WRKSRC} ; ${SETENV} LANG=C LC_ALL=C ${TCSH} -c source ${FREEBSD_ENV_SET} ; setenv TMP ${WRKSRC} ; cd instsetoo_native ; build.pl -P${MAKE_JOBS_NUMBER} --all
.else
@cd ${WRKSRC} ; ${SETENV} LANG=C LC_ALL=C ${TCSH} -c source ${FREEBSD_ENV_SET} ; setenv TMP ${WRKSRC} ; dmake
.endif
diff -ur /usr/ports/editors/openoffice.org-2-RC/Makefile ports/editors/openoffice.org-2-RC/Makefile
--- /usr/ports/editors/openoffice.org-2-RC/Makefile 2009-01-25 10:45:45.0 +0200
+++ ports/editors/openoffice.org-2-RC/Makefile 2009-05-27 08:41:53.0 +0200
@@ -52,6 +52,7 @@
USE_PERL5= yes
USE_BZIP2= yes
WITHOUT_CPU_CFLAGS= true
+MAKE_JOBS_SAFE= yes
.include bsd.port.pre.mk
@@ -134,7 +135,6 @@
CONFIGURE_WRKSRC= ${WRKSRC}/config_office
TCSH?= /bin/tcsh
PKGMESSAGE= ${WRKDIR}/pkg-message
-NUMOFPROCESSES?= 1
CONFIGURE_ARGS+= --with-gnu-cp=${LOCALBASE}/bin/gcp \
--with-gnu-patch=${LOCALBASE}/bin/gpatch \
@@ -194,8 +194,8 @@
do-build:
@cd ${WRKSRC} ; ./bootstrap
# PR:84786 #i53289#
-.if (${NUMOFPROCESSES}1)
- @cd ${WRKSRC} ; ${SETENV} LANG=C LC_ALL=C ${TCSH} -c source ${FREEBSD_ENV_SET} ; setenv TMP ${WRKSRC} ; cd instsetoo_native ; build.pl -P${NUMOFPROCESSES} --all
+.if !defined(DISABLE_MAKE_JOBS)
+ @cd ${WRKSRC} ; ${SETENV} LANG=C LC_ALL=C ${TCSH} -c source ${FREEBSD_ENV_SET} ; setenv TMP ${WRKSRC} ; cd instsetoo_native ; build.pl -P${MAKE_JOBS_NUMBER} --all
.else
@cd ${WRKSRC} ; ${SETENV} LANG=C LC_ALL=C ${TCSH} -c source ${FREEBSD_ENV_SET} ; setenv TMP ${WRKSRC} ; dmake
.endif
diff -ur /usr/ports/editors/openoffice.org-2-devel/Makefile ports/editors/openoffice.org-2-devel/Makefile
--- /usr/ports/editors/openoffice.org-2-devel/Makefile 2009-01-25 10:45:45.0 +0200
+++ ports/editors/openoffice.org-2-devel/Makefile 2009-05-27 08:46:03.0 +0200
@@ -52,6 +52,7 @@
USE_PERL5= yes
USE_BZIP2= yes
WITHOUT_CPU_CFLAGS= true
+MAKE_JOBS_SAFE= yes
.include bsd.port.pre.mk
@@
Re: emulators/linux_base-f10 = Fedora 8?
Boris Samorodov wrote: On Mon, 25 May 2009 20:49:50 +0100 Steven Hartland wrote: Why does emulators/linux_base-f10 contain a Fedora 8 port most confusing! It was just a repocopy. I'm working on it, just enotime now. Then mark the port BROKEN, or some such. User confusion is a bad thing. :) Doug ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Martin Wilke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy,
First of all sorry for all unanswered mails, I got a stupid flu,
but now i feel better... ok now back to vbox, time for a new call
for testing :-)
Following was added/fixed:
- - ACPI Support was added
- - hostDVD support was added
- - Fix startup on HEAD
- - Plist problem under AMD64 was fixed
- - Qt4 Frontend is now Optional
- - Desktop file was added
- - Xorg dependencies was fixed
- - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com)
Open task:
We have got 2 patches for nls support and the request
to make dbus and pulseaudio optional. These both will
be added with the next run.
We'd like to say many many thanks for all your feedback.
http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz
Happy Testing :-)
- --
+---+---+
| PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| Skype : splash_111 | Mail : miwi(at)FreeBSD.org |
+---+---+
| Mess with the Best, Die like the Rest! |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti
wwQAn2r0W/12iidjOfgvX05QPNQX1oUc
=b8tt
-END PGP SIGNATURE-
___
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
Hi,
first thanks for all those who participated in the port! Being able to
run VirtualBox on FreeBSD is really cool!
Well, I have one slight Problem, however, with VirtualBox on FreeBSD;
tried both the SVN-Version (since it's first days when it didn't work on
amd64, updating it each time Martin announced some good news) and the
virtualbox_5.tgz (to make sure it's not an unsupported SVN-Version
that's causing the trouble):
The /usr/local/lib/virtualbox Directory is being created root:wheel with
Mode 700.
[bash]beaster:~$ls -lad /usr/local/lib/virtualbox
drwx-- 2 root wheel 512 27 Mai 18:58 /usr/local/lib/virtualbox
The make deinstall really removes that Directory and make reinstall
does create it;
=== Generating temporary packing
list
=== Checking if emulators/virtualbox already
installed
/bin/mkdir -p
/boot/modules
install -o root -g wheel -m 555
/home/ralf/vbox2/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/release/bin/vboxdrv.ko
/boot/modules
/bin/mkdir -p
/usr/local/lib/virtualbox
(cd
/home/ralf/vbox2/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/release/bin
/bin/sh -c '(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1
/dev/null 21) /usr/sbin/chown -R root:wheel $1
/usr/bin/find -d $0 $2 -type d -exec chmod 755 $1/{} \;
/usr/bin/find -d $0 $2 -type f -exec chmod 444 $1/{} \;' -- *.so *.gc
*.r0 components
/usr/local/lib/virtualbox)
/bin/mkdir -p
/usr/local/bin
The toor-Users umask is 0022, the root Users 22.
This happens on
7.2-STABLE FreeBSD 7.2-STABLE #0: Sat May 23 17:58:51 CEST 2009
amd64
As I'm the only one who runs into this problem it must be a local
Problem; however, I have no Idea what the reason might be. Creating a
Directory being root (or toor; to be sure I tried both) works fine and
observes the umask
[-su]beaster:virtualbox$mkdir /usr/local/lib/virtualbox2
[-su]beaster:virtualbox$ls -lad /usr/local/lib/virtualbox2/
drwxr-xr-x 2 root wheel 512 May 27 19:05 /usr/local/lib/virtualbox2/
I hope I didn't overlook something in the Port's Docs; I only found
Running VirtualBox as non-root user may fail so I assume it's uspposed
to work for non-root Users, too.
Does anyone have a hint? It's not too bad having to chmod
/usr/local/lib/virtualbox, but creating with the correct permissions
would really be nice :-)
Cheers,
_ralf_
___
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
Re: [CFT] FreeBSD python25 move to python26 as default version.
Kelly Hays wrote: On Sun, May 17, 2009 at 11:54 AM, Martin Wilke m...@freebsd.org wrote: Once the installed Python has been updated to 2.6, by using one of the methods above, it is required to run the upgrade-site-packages target in lang/python to assure that site-packages are made available to the new Python version. # cd /usr/ports/lang/python make upgrade-site-packages This Makefile target requires ports-mgmt/portupgrade to be installed. A lot of us are no longer using ports-mgmt/portupgrade in favor of ports-mgmt/portmaster. Please support both tools. First, I don't use python, so I'm not directly affected by this. Second, I don't think it's reasonable to _require_ that a user needs to use any additional tools (such as portupgrade or portmaster) to do something with the ports system. I do think it's reasonable to provide instructions such as, If you use toolA, do X, for toolB do Y, and if you don't use a tool do Z, etc. That said, if someone can explain what it is that needs to be done, I will be glad to help write instructions for doing it with portmaster. Doug -- This .signature sanitized for your protection ___ 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
Re: pkg_add errors
Dominic Fandrey píše v st 27. 05. 2009 v 18:43 +0200: During my last run of 'pkg_upgrade -a', cups-client forgot to install the library libcups.so.2, which I fortunately recognized due to my routine of running pkg_libchk after every package/port upgrade. Running 'pkg_upgrade cups-client' fixed that problem. The interesting part is, that the reinstallation of cups-client was done from the same package. So either pkg_add, tar or the file system were to blame, because the package is without fault. I expect that this unreliability of pkg_add (or the underlying systems) has a severe impact on my further development of pkg_upgrade. I think it was entirely different story -- installation of cups-client (put libcups on disc) upgrade of cups-base (remove libcups from disc) -- Pav Lucistnik p...@oook.cz p...@freebsd.org 94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: emulators/linux_base-f10 = Fedora 8?
It was just a repocopy. I'm working on it, just enotime now. Then mark the port BROKEN, or some such. User confusion is a bad thing. :) s/BROKEN/IGNORE/ mcl ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Martin Wilke wrote: http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz On a newly up to date -current (r192914) with world and kernel in synch and ports up to date I get the same panic when trying to kldload vboxdrv. This is on a C2D running i386 SMP. panic: boot: not running on cpu0 cupid = 1 Also, I got the following when trying to build with debug. Building without debug worked. hth, Doug kBuild: Compiling vboxdrv - /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c kBuild: Compiling vboxdrv - /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c: In function 'supdrvIOCtl': /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c:1429: warning: format '%#lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int' /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/SUPDrv.c:1610: warning: format '%#lx' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kmk[2]: *** [/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 The failing command: @gcc -c -g -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -Wpointer-arith -Winline -Wno-pointer-sign -Wstrict-prototypes -Wmissing-prototypes -Wstrict-prototypes -Wnested-externs -O2 -fformat-extensions -ffreestanding -fno-strict-aliasing -fno-common -finline-limit=8000 -fno-stack-protector -march=i586 -O0 -fno-omit-frame-pointer -nostdinc -std=c99 -m32 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -I/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/../include -I/usr/include -I/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/include -I/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\/usr/local/lib/virtualbox\ -DRTPATH_APP_PRIVATE_ARCH=\/usr/local/lib/virtualbox\ -DRTPATH_SHARED_LIBS=\/usr/local/lib/virtualbox\ -DRTPATH_APP_DOCS=\/usr/local/share/doc/virtualbox\ -DDEBUG -DDEBUG_dougb -DDEBUG_USERNAME=dougb -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -D_KERNEL -DKLD_MODULE -DIN_RING0 -DIN_RT_R0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_SVN_REV=19957 -Wp,-MD,/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o.dep -Wp,-MT,/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o -Wp,-MP -o /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.x86/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o /usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c kmk[2]: *** Waiting for unfinished jobs kmk[2]: Leaving directory `/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980' kmk[2]: Entering directory `/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_binaries_this] Error 2 kmk[1]: Leaving directory `/usr/local/home/dougb/virtualbox/work/virtualbox-2.2.2r19980' kmk: *** [pass_binaries_order] Error 2 *** Error code 2 Stop in /usr/local/home/dougb/virtualbox. *** Error code 1 Stop in /usr/local/home/dougb/virtualbox. -- This .signature sanitized for your protection ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
-CURRENT/amd64 as of yesterday. First, there's a build issue: /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDOpen': /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:299: error: invalid operands to binary /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c: In function 'VBoxDrvFreeBSDClose': /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c:355: error: invalid operands to binary kBuild: Linking tstCollector kmk[2]: *** [/gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/out/freebsd.amd64/debug/obj/vboxdrv/freebsd/SUPDrv-freebsd.o] Error 1 Looks like a problem with minor() macro use. Patched it up to print raw pointer instead and move on with compilation. During installation I had to manually fetch http://download.virtualbox.org/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso into /usr/ports/distfiles -- this has already been reported, I believe. The bad news is that kernel crashed on load of vboxdrv: VBoxDrvFreeBSDLoad: 7/1: off=ae6 6/1: off=20870d6 5/1: off=20a420f 4/1: off=20ab06a 3/1: off=20acf63 2/1: off=20a5eec 1/1: off=20a9bc7 0/1: off=20a6cbd supdrvDetermineAsyncTsc: returns 0; iLastCpu=3 rc=-801 offMin=ae6 offMax=20acf63 vboxdrv: fAsync=0 offMin=0xae6 offMax=0x20acf63 supdrvGipCreate: 1000 ns interval. VBoxDrvFreeBSDLoad: returns successfully !!Assertion Failed!! Expression: cMillies != RT_INDEFINITE_WAIT Location : /gm0/zm0/home/artem/vbox/virtualbox/work/virtualbox-2.2.2r19980/src/VBox/Runtime/r0drv/freebsd/semevent-r0drv-freebsd.c(212) rtSemEventWait [thread pid 58317 tid 100567 ] Stopped at rtSemEventWait+0x39a: nop db where Tracing pid 58317 tid 100567 td 0xff00909f8390 rtSemEventWait() at rtSemEventWait+0x39a RTSemEventWait() at RTSemEventWait+0x20 _Z13rtTimerThreadP11RTTHREADINTPv() at _Z13rtTimerThreadP11RTTHREADINTPv+0x44 rtThreadMain() at rtThreadMain+0x121 rtThreadNativeMain() at rtThreadNativeMain+0x35 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xff842fcb5d40, rbp = 0 --- db --Artem On Wed, May 27, 2009 at 6:43 AM, Martin Wilke m...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Happy Testing :-) - -- +---+---+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkodQ48ACgkQdLJIhLHm/OmjfQCfR6Zczz0XcZZpAYie64D2G0Ti wwQAn2r0W/12iidjOfgvX05QPNQX1oUc =b8tt -END PGP SIGNATURE- ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ 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
Re: pkg_add errors
Hello Dominic, List, Thanks for your work, much appreciated. Dominic Fandrey kamik...@bsdforen.de writes: I need something similar for the incomplete package problem. Should pkg_upgrade create a summary of apparently broken packages that have been installed? I would go with this option since one can use not only official packages but home made ones (and without much testing). Should it bail out (and break with every package that has a broken plist)? That imho would be a little bit draconian. BTW, current behaviour of pkg_upgrade -F to stop at the first package that can't be downloaded is the same. Can this behaviour be changed to proceeding but printing out the list of not downloaded packages at the end? Or at least can you create an option for such behaviour? Should it perform library checks That may be done via command line option. and try to auto fix them? That task seems to be very hard to achieve. My preference would be to rely on 'pkg_info -g', but that would require all committers to run extensive checks before committing changes to the ports tree. Miwi has always done this and more than once revealed PLIST problems of my ports to me. But I wonder whether it is really sensible to ask committers to test everything on a Tinderbox (preferably on several platforms) before committing changes to the ports tree. Hm, ports with broken PLISTS are, well, broken. And should be fixed or marked BROKEN. I was sure that the FreeBSD packaging cluster does not produce packages with broken plists (i.e. the package is not created). Is that wrong? WBR -- bsam ___ 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
Re: [CFT] FreeBSD python25 move to python26 as default version.
On Wed, May 27, 2009 at 10:58:05AM -0700, Doug Barton wrote:
Kelly Hays wrote:
On Sun, May 17, 2009 at 11:54 AM, Martin Wilke m...@freebsd.org wrote:
Once the installed Python has been updated to 2.6, by using one of the
methods above, it is required to run the upgrade-site-packages target in
lang/python to assure that site-packages are made available to the new
Python
version.
# cd /usr/ports/lang/python make upgrade-site-packages
This Makefile target requires ports-mgmt/portupgrade to be installed.
A lot of us are no longer using ports-mgmt/portupgrade in favor of
ports-mgmt/portmaster. Please support both tools.
First, I don't use python, so I'm not directly affected by this.
Second, I don't think it's reasonable to _require_ that a user needs
to use any additional tools (such as portupgrade or portmaster) to do
something with the ports system. I do think it's reasonable to provide
instructions such as, If you use toolA, do X, for toolB do Y, and if
you don't use a tool do Z, etc.
That said, if someone can explain what it is that needs to be done, I
will be glad to help write instructions for doing it with portmaster.
At first glance it looks like pkg_which can be replaced with
'pkg_info -W' (the grep stuff may have to be changed, I haven't looked
into it) and the portupgrade piece can be replaced with the
equivalent in portmaster. There could be an
upgrade-site-packages-portmaster target or the equivalent instructions
can be added to UPDATING.
# Major upgrade support
PORTUPGRADE_CMD?= ${LOCALBASE}/sbin/portupgrade
PKG_WHICH_CMD?= ${LOCALBASE}/sbin/pkg_which
upgrade-site-packages:
@if [ ! -x ${PORTUPGRADE_CMD} ]; then \
${ECHO_MSG} Please install ports-mgmt/portupgrade.; \
${FALSE}; \
fi
@for ver in `echo ${_PYTHON_ALLBRANCHES}|${SED} 's/${PYTHON_VER}//'`;
do \
if [ -d ${PREFIX}/lib/python$$ver ]; then \
UPD=`${FIND} ${PREFIX}/lib/python$$ver \
-type f -print0 | \
${XARGS} -0 ${PKG_WHICH_CMD} | \
${GREP} -Fv '?' | \
${EGREP} -v '^python2?[0-5]?-2' | \
${SORT} -u`; \
if [ $$UPD ]; then \
${PORTUPGRADE_CMD} -f $$UPD; \
fi; \
fi; \
done \
-- WXS
___
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
Re: [CFT] FreeBSD python25 move to python26 as default version.
Wesley Shields wrote:
On Wed, May 27, 2009 at 10:58:05AM -0700, Doug Barton wrote:
Kelly Hays wrote:
On Sun, May 17, 2009 at 11:54 AM, Martin Wilke m...@freebsd.org wrote:
Once the installed Python has been updated to 2.6, by using one of the
methods above, it is required to run the upgrade-site-packages target in
lang/python to assure that site-packages are made available to the new
Python
version.
# cd /usr/ports/lang/python make upgrade-site-packages
This Makefile target requires ports-mgmt/portupgrade to be installed.
A lot of us are no longer using ports-mgmt/portupgrade in favor of
ports-mgmt/portmaster. Please support both tools.
First, I don't use python, so I'm not directly affected by this.
Second, I don't think it's reasonable to _require_ that a user needs
to use any additional tools (such as portupgrade or portmaster) to do
something with the ports system. I do think it's reasonable to provide
instructions such as, If you use toolA, do X, for toolB do Y, and if
you don't use a tool do Z, etc.
That said, if someone can explain what it is that needs to be done, I
will be glad to help write instructions for doing it with portmaster.
At first glance it looks like pkg_which can be replaced with
'pkg_info -W' (the grep stuff may have to be changed, I haven't looked
into it) and the portupgrade piece can be replaced with the
equivalent in portmaster. There could be an
upgrade-site-packages-portmaster target or the equivalent instructions
can be added to UPDATING.
Thanks for taking a look at this. I tend to agree with you that it
should be easy to replace. For that matter, it should even be possible
to replace the portupgrade piece with 'make -DFORCE_PKG_REGISTER' but
I certainly wouldn't deny people who use the various maintenance tools
the opportunity to use them.
FWIW, portmaster does the equivalent of 'portupgrade -f' by default,
so the equivalent in the code below would simply be:
${PORTMASTER_CMD} $$UPD;
hope this helps,
Doug
# Major upgrade support
PORTUPGRADE_CMD?= ${LOCALBASE}/sbin/portupgrade
PKG_WHICH_CMD?= ${LOCALBASE}/sbin/pkg_which
upgrade-site-packages:
@if [ ! -x ${PORTUPGRADE_CMD} ]; then \
${ECHO_MSG} Please install ports-mgmt/portupgrade.; \
${FALSE}; \
fi
@for ver in `echo ${_PYTHON_ALLBRANCHES}|${SED} 's/${PYTHON_VER}//'`;
do \
if [ -d ${PREFIX}/lib/python$$ver ]; then \
UPD=`${FIND} ${PREFIX}/lib/python$$ver \
-type f -print0 | \
${XARGS} -0 ${PKG_WHICH_CMD} | \
${GREP} -Fv '?' | \
${EGREP} -v '^python2?[0-5]?-2' | \
${SORT} -u`; \
if [ $$UPD ]; then \
${PORTUPGRADE_CMD} -f $$UPD; \
fi; \
fi; \
done \
-- WXS
___
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
___
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
Re: pkg_add errors
Pav Lucistnik wrote: Dominic Fandrey píše v st 27. 05. 2009 v 18:43 +0200: During my last run of 'pkg_upgrade -a', cups-client forgot to install the library libcups.so.2, which I fortunately recognized due to my routine of running pkg_libchk after every package/port upgrade. Running 'pkg_upgrade cups-client' fixed that problem. The interesting part is, that the reinstallation of cups-client was done from the same package. So either pkg_add, tar or the file system were to blame, because the package is without fault. I expect that this unreliability of pkg_add (or the underlying systems) has a severe impact on my further development of pkg_upgrade. I think it was entirely different story -- installation of cups-client (put libcups on disc) upgrade of cups-base (remove libcups from disc) Well, that's possible, but why would cups-base perform such an evil deed? It's a very soothing suggestion, though. At least as far as pkg_upgrade is concerned. ___ 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
Re: pkg_add errors
On Thu, 28 May 2009 01:20:17 +0400 Boris Samorodov b...@ipt.ru wrote: [ .. ] My preference would be to rely on 'pkg_info -g', but that would require all committers to run extensive checks before committing changes to the ports tree. Miwi has always done this and more than once revealed PLIST problems of my ports to me. But I wonder whether it is really sensible to ask committers to test everything on a Tinderbox (preferably on several platforms) before committing changes to the ports tree. We do encourage this. The preferably on several platforms is problematic due to available resources we each have. Hm, ports with broken PLISTS are, well, broken. And should be fixed or marked BROKEN. And they are. I'm actively marking them broken based on QAT. I can't do it instantly since some people require patting on the head ... I was sure that the FreeBSD packaging cluster does not produce packages with broken plists (i.e. the package is not created). Is that wrong? No, plist problems are hard errors. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: pkg_add errors
Dominic Fandrey wrote: Pav Lucistnik wrote: Dominic Fandrey píše v st 27. 05. 2009 v 18:43 +0200: During my last run of 'pkg_upgrade -a', cups-client forgot to install the library libcups.so.2, which I fortunately recognized due to my routine of running pkg_libchk after every package/port upgrade. Running 'pkg_upgrade cups-client' fixed that problem. The interesting part is, that the reinstallation of cups-client was done from the same package. So either pkg_add, tar or the file system were to blame, because the package is without fault. I expect that this unreliability of pkg_add (or the underlying systems) has a severe impact on my further development of pkg_upgrade. I think it was entirely different story -- installation of cups-client (put libcups on disc) upgrade of cups-base (remove libcups from disc) Well, that's possible, but why would cups-base perform such an evil deed? Stupid me, I just read UPDATING. That explains everything. But that puts the question forward how to deal with this. People using pkg_upgrade do not require a ports tree and hence do not have UPDATING. It's a very soothing suggestion, though. At least as far as pkg_upgrade is concerned. ___ 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
Re: pkg_add errors
Boris Samorodov wrote: Hello Dominic, List, Thanks for your work, much appreciated. You're welcome. Dominic Fandrey kamik...@bsdforen.de writes: I need something similar for the incomplete package problem. Should pkg_upgrade create a summary of apparently broken packages that have been installed? I would go with this option since one can use not only official packages but home made ones (and without much testing). I suppose. So this goes into the list of feature requests. Should it bail out (and break with every package that has a broken plist)? That imho would be a little bit draconian. Pav Lucistnik suggested cups-base was to blame. Well, I just read /usr/ports/UPDATING and this is definitely one of the things that cannot be dealt with automatically. BTW, current behaviour of pkg_upgrade -F to stop at the first package that can't be downloaded is the same. Can this behaviour be changed to proceeding but printing out the list of not downloaded packages at the end? Or at least can you create an option for such behaviour? Should it perform library checks That may be done via command line option. and try to auto fix them? That task seems to be very hard to achieve. I've actually put some thought on this. It's been on the list of planned features for a long time. I'm pretty certain, I can deal with a large majority of library problems without human interaction. What irks me about it is that the sequence of actions would be broken by this. Features like fetching in advance and performing updates later would break. And all these problems could be avoided if library changes always resulted in a version bump of all dependencies. A path that has been followed more often recently, but still cannot be relied on. My preference would be to rely on 'pkg_info -g', but that would require all committers to run extensive checks before committing changes to the ports tree. Miwi has always done this and more than once revealed PLIST problems of my ports to me. But I wonder whether it is really sensible to ask committers to test everything on a Tinderbox (preferably on several platforms) before committing changes to the ports tree. Hm, ports with broken PLISTS are, well, broken. And should be fixed or marked BROKEN. I was sure that the FreeBSD packaging cluster does not produce packages with broken plists (i.e. the package is not created). Is that wrong? I think so. After all the Pointyhead packages are built from the same ports tree as the one everyone else uses. And that has a couple of persistently broken plists, not many, but some. WBR ___ 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
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
From: Martin Wilke m...@freebsd.org Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 Date: Wed, 27 May 2009 15:43:43 +0200 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - - ACPI Support was added - - hostDVD support was added - - Fix startup on HEAD - - Plist problem under AMD64 was fixed - - Qt4 Frontend is now Optional - - Desktop file was added - - Xorg dependencies was fixed - - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Hi Martin, E-mail address might be m...@freebsd.org :) thank you -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt pgpK8zEZ6lyTO.pgp Description: PGP signature
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
On Wed, 27 May 2009, Martin Wilke wrote: First of all sorry for all unanswered mails, I got a stupid flu, but now i feel better... ok now back to vbox, time for a new call for testing :-) Following was added/fixed: - ACPI Support was added - hostDVD support was added - Fix startup on HEAD - Plist problem under AMD64 was fixed - Qt4 Frontend is now Optional - Desktop file was added - Xorg dependencies was fixed - Guest additions was added (thx to Maho NAKATA chat95 (at) mac dot com) Nice :) It works for me on -current/i386 (but they have all done so) however it did crash after I started the new VBox (I unloaded the old KLD, loaded the new one, start VM - crash). Unfortunately X was running so it just reset with no crash dump. However the guest addition stuff didn't work properly for me.. I ran make config and selected it, vbox built, but at install time I got.. /bin/chmod 0711 /usr/local/lib/virtualbox/VBoxSVC /bin/chmod 0711 /usr/local/lib/virtualbox/VBoxXPCOMIPCD install -o root -g wheel -m 444 /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso /usr/local/lib/virtualbox/ install: /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso: No such file or directory *** Error code 71 Stop in /usr/home/darius/projects/virtualbox. *** Error code 1 Stop in /usr/home/darius/projects/virtualbox. and that file is missing, if I do make fetch it doesn't download it either. If I do make fetch WITH_GUESTADDITIONS= it does download it. Open task: We have got 2 patches for nls support and the request to make dbus and pulseaudio optional. These both will be added with the next run. We'd like to say many many thanks for all your feedback. http://people.freebsd.org/~miwi/vbox/virtualbox_5.tgz Are there plans (or patches :) for adding other types of network support? NAT is usable but without the ability to forward ports it makes logging in via SSH rather tedious (ie log out from the VM with -R then log back in). Thanks for your work thus far, it's a very handy tool :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: [Call For Testing] VirtualBox for FreeBSD! take 4
Hi miwi, In some environment, to fetch VBoxGuestAdditions_2.2.2.iso correctly, you must add FETCH_ARGS=-pRr (remove A). Note, somehow in virtualbox_5.tgz FETCH_ARGS=-pRr was removed. Thanks From: Daniel O'Connor docon...@gsoft.com.au Subject: Re: [Call For Testing] VirtualBox for FreeBSD! take 4 Date: Thu, 28 May 2009 12:31:17 +0930 444 /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso /usr/local/lib/virtualbox/ install: /usr/ports/distfiles/VBoxGuestAdditions_2.2.2.iso: No such file and that file is missing, if I do make fetch it doesn't download it either. -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt pgpndd9t2BHUd.pgp Description: PGP signature
Re: MAKE_JOBS_UNSAFE (some more ports)
Hi David, I'll go to Canada for attending conference tomorrow.be back on 6/4. see you -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ Nakata Maho's PGP public keys: http://accc.riken.jp/maho/maho.pgp.txt pgpVkDXepD1Ih.pgp Description: PGP signature
