Re: MAKE_JOBS_UNSAFE (some more ports)
Hi David Many many thanks for your patch. I'll test it very soon. Just one comment I believe openoffice-2* can me marked as SAFE while openoffice-3* should not be marked at all (since it sometimes works..., very well for me :-). you can mark as SAFE for all of our ports. If it's broken, its OOo issue. We should identify if dependencies are missing. -devel ports can be unsafe but 3, 3-RC 2, 2-RC must be safe. Please wait a few days to say ok. Best, From: David Naylor naylor.b.da...@gmail.com Subject: Re: MAKE_JOBS_UNSAFE (some more ports) Date: Sat, 23 May 2009 11:01:56 +0200 On Friday 22 May 2009 15:41:38 Ion-Mihai Tetcu wrote: On Fri, 22 May 2009 19:53:50 +0900 (JST) Maho NAKATA cha...@mac.com wrote: In massive parallel build, OOo can be broken. We explicitly fix them otherwise broken. I just test with MAXJOB = 4 or something like that. I had it complain about perl (or something) needing to be recompiled but that was because I interrupted the build process. It has always completed for me when using MAX* from the start. me too. but - note it just works for you. I can make the patch, only thing is bsd.port.mk will need to be patched (simple enough though). I can run a few test builds on QAT and maybe Phillip can do the same on his tindy. Just drop us the patch ;-) Even if it only works with MAXJOB = 2, we mark it as such and the build will be faster. Please see attached for the patch. The changes to bsd.port.mk: - MAKE_JOBS_NUMBER always defined - MAKE_JOBS_NUMBER forced to 1 if UNSAFE of DISABLE - MAKE_JOBS_NUMBER defaults (but user defined) to number of cores I've then used MAKE_JOBS_NUMBER to set MAXPROCESSES, MAXMODULES and NUMOFPROCESSES for openoffice-* (not including 1.*). I believe openoffice-2* can me marked as SAFE while openoffice-3* should not be marked at all (since it sometimes works..., very well for me :-). This patch just makes openoffice-* behave like other ports in regards to parallel builds and the usual MAKE_JOBS variables now works as expected. Happy testing, David pgpq2xMEndG96.pgp Description: PGP signature
Re: MAKE_JOBS_UNSAFE (some more ports)
On Sat, 23 May 2009 18:24:26 +0900 (JST)
Maho NAKATA cha...@mac.com wrote:
Hi David
Many many thanks for your patch. I'll test it very soon.
Just one comment
I believe openoffice-2* can me marked as SAFE while openoffice-3*
should not be marked at all (since it sometimes works..., very well
for me :-).
you can mark as SAFE for all of our ports.
For testing, right?
If it's broken, its OOo issue.
Obviously.
We should identify if dependencies are missing. -devel ports can be
unsafe but 3, 3-RC 2, 2-RC must be safe.
Please wait a few days to say ok.
I'll give them a try during this weekend.
From: David Naylor naylor.b.da...@gmail.com
Subject: Re: MAKE_JOBS_UNSAFE (some more ports)
Date: Sat, 23 May 2009 11:01:56 +0200
[ .. ]
Please see attached for the patch. The changes to bsd.port.mk:
- MAKE_JOBS_NUMBER always defined
- MAKE_JOBS_NUMBER forced to 1 if UNSAFE of DISABLE
AFAIR there are ports that compile OK w/o MAKE_JOBS_SAFE but fail with
MAKE_JOBS_NUMBER=1
- MAKE_JOBS_NUMBER defaults (but user defined) to number of cores
This part looks OK, I wonder if there's any reason t ain't like this
now; Pav?
-.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
I believe pav@ didn't put the ' !defined(MAKE_JOBS_SAFE)' part
intentionally until we get to test all our ports.
-.if defined(FORCE_MAKE_JOBS)
+.if defined(FORCE_MAKE_JOBS) !defined(MAKE_JOBS_SAFE)
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.
I've then used MAKE_JOBS_NUMBER to set MAXPROCESSES, MAXMODULES and
NUMOFPROCESSES for openoffice-* (not including 1.*).
I believe openoffice-2* can me marked as SAFE while openoffice-3*
should not be marked at all (since it sometimes works..., very well
for me :-).
This patch just makes openoffice-* behave like other ports in
regards to parallel builds and the usual MAKE_JOBS variables now
works as expected.
Nice, thanks.
--
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: MAKE_JOBS_UNSAFE (some more ports)
On Saturday 23 May 2009 12:51:33 Ion-Mihai Tetcu wrote:
On Sat, 23 May 2009 18:24:26 +0900 (JST)
Maho NAKATA cha...@mac.com wrote:
Please see attached for the patch. The changes to bsd.port.mk:
- MAKE_JOBS_NUMBER always defined
- MAKE_JOBS_NUMBER forced to 1 if UNSAFE of DISABLE
AFAIR there are ports that compile OK w/o MAKE_JOBS_SAFE but fail with
MAKE_JOBS_NUMBER=1
That is quite a problem. And this reveals a problem with openoffice-2*, it
doesn't work since it does (in-effect):
.if (${MAKE_JOBS_NUMBER} 1)
which will not work for MAKE_JOBS_NUMBER=`${SYSCTL} -n kern.smp.cpus`. Is
there anyway for MAKE_JOBS_NUMBER to get a resolved value (I think expanding
make to expose the number of cores on the system [rather radical, I know]).
If MAKE_JOBS_NUMBER can be 'fixed' then the solution is straight forward:
.if (${MAKE_JOBS_NUMBER} 1)
# Use concurrent build
.else
# Use standard build
.endif
- MAKE_JOBS_NUMBER defaults (but user defined) to number of cores
This part looks OK, I wonder if there's any reason t ain't like this
now; Pav?
-.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
I believe pav@ didn't put the ' !defined(MAKE_JOBS_SAFE)' part
intentionally until we get to test all our ports.
-.if defined(FORCE_MAKE_JOBS)
+.if defined(FORCE_MAKE_JOBS) !defined(MAKE_JOBS_SAFE)
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.
Sorry but I don't see how this would change anything. The message will only
get displayed if the port fails AND -DFORCE_MAKE_JOBS, which is the less
likely scenario.
I only changed it because when testing the command output with `make build -n`
the offset changed with -DFORCE_MAKE_JOBS on a safe port. I just found it
annoying...
I've then used MAKE_JOBS_NUMBER to set MAXPROCESSES, MAXMODULES and
NUMOFPROCESSES for openoffice-* (not including 1.*).
I believe openoffice-2* can me marked as SAFE while openoffice-3*
should not be marked at all (since it sometimes works..., very well
for me :-).
This patch just makes openoffice-* behave like other ports in
regards to parallel builds and the usual MAKE_JOBS variables now
works as expected.
Nice, thanks.
signature.asc
Description: This is a digitally signed message part.
Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3
Hi miwi,
Here is a patch adding WITH_GUESTADDITIONS knob.
With this knob we also installs
Guest additions.iso. This driver makes Windows XP, Linux and Solaris faster.
I'm a newbie to VirtualBox so it is not the correct patch.
I don't check it thoroughly but ISO image itself is not a GPL one.
Best,
--- Makefile2009-05-23 01:59:37.0 +0900
+++ Makefile2009-05-23 21:14:52.0 +0900
@@ -6,16 +6,26 @@
#
PORTNAME= virtualbox
-PORTVERSION= 2.2.2r19852
+PORTVERSION= ${VBOXVER}r19852
CATEGORIES=emulators kld
MASTER_SITES= http://tmp.chruetertee.ch/ \
http://freebsd.unixfreunde.de/sources/ \
http://disasterarea.chruetertee.ch/ \
http://mirror.4bit.ws/
+.if defined(WITH_GUESTADDITIONS)
+MASTER_SITES+= http://dlc.sun.com/virtualbox/${VBOXVER}/:guestadditons
+DISTFILES= ${DISTNAME}${EXTRACT_SUFX} ${GUESTADDITIONS}:guestaddtions
+EXTRACT_ONLY= ${DISTNAME}${EXTRACT_SUFX}
+.endif
MAINTAINER=de...@bluelife.at
COMMENT= A general-purpose full virtualizer for x86 hardware
+VBOXVER= 2.2.2
+FETCH_ARGS=-pRr
+GUESTADDITIONS_GENERICNAME=VBoxGuestAdditions.iso
+GUESTADDITIONS=VBoxGuestAdditions_${VBOXVER}.iso
+
BUILD_DEPENDS= yasm:${PORTSDIR}/devel/yasm \
as86:${PORTSDIR}/devel/dev86 \
xsltproc:${PORTSDIR}/textproc/libxslt \
@@ -52,6 +62,9 @@
KMODDIR= /boot/modules
PLIST_SUB+=KMODDIR=${KMODDIR}
+.if defined(WITH_GUESTADDITIONS)
+PLIST_FILES+= lib/virtualbox/${GUESTADDITIONS}
lib/virtualbox/${GUESTADDITIONS_GENERICNAME}
+.endif
KMK_CONFIG=VBOX_LIBPATH_X11=${LOCALBASE}
@@ -127,7 +140,10 @@
${MKDIR} ${PREFIX}/lib/virtualbox
(cd ${WRKSRC}/out/${KMK_ARCH}/release/bin ${COPYTREE_SHARE} *.so
*.gc *.r0 components ${PREFIX}/lib/virtualbox)
-
+.if defined(WITH_GUESTADDITIONS)
+ ${INSTALL_DATA} ${DISTDIR}/${GUESTADDITIONS} ${PREFIX}/lib/virtualbox/
+ ${LN} -sf ${PREFIX}/lib/virtualbox/${GUESTADDITIONS}
${PREFIX}/lib/virtualbox/${GUESTADDITIONS_GENERICNAME}
+.endif
${MKDIR} ${PREFIX}/bin
.for f in VBoxBFE VBoxHeadless VBoxManage VBoxNetDHCP VBoxSDL VBoxSVC
VBoxXPCOMIPCD VirtualBox
${INSTALL_PROGRAM} ${WRKSRC}/out/${KMK_ARCH}/release/bin/$f
${PREFIX}/lib/virtualbox/
--- distinfo2009-05-23 01:59:37.0 +0900
+++ distinfo2009-05-23 20:17:28.0 +0900
@@ -1,3 +1,6 @@
MD5 (virtualbox-2.2.2r19852.tar.gz) = ff1e05bd04fd7974a90e12394cb58626
SHA256 (virtualbox-2.2.2r19852.tar.gz) =
7b898c643551f5b74d169a79ad41801cc5675b5e57a7da0f700875dd11265a5f
SIZE (virtualbox-2.2.2r19852.tar.gz) = 58070688
+MD5 (VBoxGuestAdditions_2.2.2.iso) = 9c09a9e88abe9edd8fec6fd3cf453535
+SHA256 (VBoxGuestAdditions_2.2.2.iso) =
3727c024d8d426443158b1063a9d7355d492da3725470c4c01fafbe4bc382687
+SIZE (VBoxGuestAdditions_2.2.2.iso) = 28755968
pgplBrHwDjDNc.pgp
Description: PGP signature
Re: A port for FireGPG?
On Sat, May 23, 2009 at 12:31:29AM +0200, cpghost wrote: Hi, I'd like to use GnuPG with Webmail (e.g. with gmail or other webmails). AFAICS, the following Firefox add-on would help: http://www.getfiregpg.org/ Unfortunately, according to http://www.getfiregpg.org/install.html one needs to compile an IPC library (?) out of the firefox3 sources, like this: http://blog.getfiregpg.org/2008/10/17/how-to-compile-the-ipc-library/ Is there a port to automate this task, or could someone with the necessary skills please create such a port? That would be great! Just a little follow-up. Those are the (manual) steps to get libipc compiled on FreeBSD/amd64, assuming www/firefox3 is already installed: # cd /usr/ports/www/firefox3 # make configure # make build (Be patient, it takes some time) # cd work/mozilla/extensions # now fetch libipc (ipc-latest.tar.gz) to /path/to/ipc-latest.zip (source of ipc-latest.tar.gz is https://bugzilla.mozilla.org/attachment.cgi?id=299132) # tar -xvpf /path/to/ipc-latest.zip # chown -R root:wheel ipc (We now have /usr/ports/www/firefox3/work/mozilla/extensions/ipc) # cd ipc now: /usr/ports/www/firefox3/work/mozilla/extensions/ipc # ./makemake -r -o . # gmake (This will create libipc.so, ipc.xpt in: /usr/ports/www/firefox3/work/mozilla/dist/bin/components) # cd /usr/ports/www/firefox3/work/mozilla/dist/bin/components # cp -i libipc.so /usr/local/lib/firefox3/components/ # cp -i ipc.xpt /usr/local/lib/firefox3/components/ (There is no need to install firefox3 again. Only libipc.so and ipc.xpt count) $ cd ~/.mozilla/firefox/the_firefox_profile $ touch .autoreg (And restart firefox3). With that, firegpg add-on works flawlessly. All this can probably be automated with a slave port of www/firefox3. Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: Adding Guestadditions.iso Re: [Call For Testing] VirtualBox for FreeBSD! take 3
On Sat, May 23, 2009 2:32 pm, Maho NAKATA wrote: Hi miwi, Here is a patch adding WITH_GUESTADDITIONS knob. With this knob we also installs Guest additions.iso. This driver makes Windows XP, Linux and Solaris faster. I'm a newbie to VirtualBox so it is not the correct patch. I don't check it thoroughly but ISO image itself is not a GPL one. Thanks, it's commited with a few modifications. -- Bernhard Fröhlich http://www.bluelife.at/ ___ 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)
Hi I tested it yesterday, 1. I need MAKE_JOBS_SAFE=yes in the Makefile. 2. with above patch, ooo2 doesn't launch parallele jobs. 3. ooo3, 3-rc, 3-devel are okay with patch 1. thanks -- 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 pgpLp4gHHSs1u.pgp Description: PGP signature
Force rebuild/reinstall dependent ports
Hello, I have some questions about port dependencies. Let's take for example following situation: I have dovecot and dovecot-managesieve installed. Today a new version of Dovecot showed up, so i'm upgrading it: # make -C /usr/port/mail/dovecot It builds ok, so i'm reinstalling port: # make -C /usr/port/mail/dovecot deinstall install clean Everything is ok, but now, when restarting i'm getting in log file: # May 24 01:10:59 vm01 dovecot: Fatal: managesieve-login: Dovecot version mismatch: Master is v1.1.15, login is v1.1.14 [...] I have to rebuild dovecot-managesieve with newer dovecot support, it's clear for me and it works after that. But why won't port do this automatically? Is there a way to force it before installing updated port version? Cheers, -- Marcin Rzepecki m.rzepecki(at)iem.pw.edu.pl ___ 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: Force rebuild/reinstall dependent ports
Sat, May 23, 2009 at 08:22:03PM -0400, Robert Huff wrote: Revuilding a dependency (here, dovecot) does not always require rebuilding the dependant port. Sometimes, but not always. Hello Robert, first, thanks for the answer. So, is there any dirty trick to make it happen? ;) For example with some adds in Makefile.local? Also: are you aware of ports-mgmt/portupgrade, ports-mgmt/portmaster, etc.? Yep, I have same problems with portmaster, that's why i'm even asking. Cheers! -- Marcin Rzepecki m.rzepecki(at)iem.pw.edu.pl ___ 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: Force rebuild/reinstall dependent ports
On Sat, 23 May 2009 20:22:03 -0400 Robert Huff roberth...@rcn.com wrote: Marcin Rzepecki writes: But why won't port do this automatically? Is there a way to force it before installing updated port version? Revuilding a dependency (here, dovecot) does not always require rebuilding the dependant port. Sometimes, but not always. Also: are you aware of ports-mgmt/portupgrade, ports-mgmt/portmaster, etc.? This kind of thing should be in UPDATING. Portmanager will update automatically, at the expense of a lot of gratuitous rebuilding. ___ 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
Fixing multimedia/audacious upgrade
Just as a note, if you upgrade multimedia/audacious and you run into the following error: $ audacious2 /libexec/ld-elf.so.1: Shared object libaudclient.so.1 not found, required by audacious2 Deinstall and recompile audacious and it should work (at least it did for me). HTH, -Garrett ___ 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
Problems with perl upgrade
I'm preparing to upgrade two servers. I decided to upgrade perl to 5.10.0 before doing anything else (I've done this before on other systems), but I ran into a problem. Per /usr/ports/UPDATING # portupgrade -o lang /perl5.10 -f perl-5.8.\*** There are errors in a meta info for perl-5.8.9 ** Run 'pkgdb -F' to interactively fix them. But when I run pkgdb: # pkgdb -F--- Checking the package registry database Checking /usr/local/lib/perl5, I have two directories; 5.8.8 and 5.8.9. How do I solve this problem? Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ 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: perl upgrade problems
Ignore my last message, just like I ignored the space between lang and /. Sorry to bother the list. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ 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
