Re: Boost 1.37 released!
I also agree with you Jeremy. devel/boost-devel makes no sense as it is a stable and not a development version.When there are so much ports that depend on devel/boost (as version 1.34) then I see two approaches to solve this. 1.) Try to find out if boost 1.37 is binary compatible with boost 1.34. If so, then we could update it to the actual version without breaking the ports depending on it, IMHO. I made this a question to the boost irc channel and got only the answer that this is doubtable so far. 2.) We should think of one or two alternative boost port(s) like devel/boost137 and devel/boost138. All depending ports must be made dependant to devel/boost137 then. Other ports also keep two ports with their (often major) release numbers and switch dependent ports back and forth to the right port release number. I'd prefer the second because there are less side effects and problems possible. Also please note that http://home.leo.org isn't accessible anymore. Hopefully someone, preferrably Alexander, has the 1.35 patch from Simon to check whether it's easy to bump the port to 1.37 easily. I also agree to send a PR. /Flex ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wacom driver
Dominic Fandrey escribió: I have created a port of Bartosz Fabianowski's Wacom driver. Since nobody has stepped forward to commit it, I thought I'd inform this list, so that people can test it. http://www.freebsd.org/cgi/query-pr.cgi?pr=128547 I suggest that you should consult with [EMAIL PROTECTED] He was going to port this driver himself but he hasn't got time so far. I've CC'd him because I don't think he is on the ports@ list because he is a doc committer. Cheers, -- Gabor Kovesdan EMAIL: [EMAIL PROTECTED] WWW: http://www.kovesdan.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/125745: Update to www/rt3* available - 3.8.0
Le 27/08/2008 à 23:51:31-0400, Philip M. Gollucci a écrit Albert Shih wrote: Le 19/08/2008 à 19:32:52-0400, Philip M. Gollucci a écrit Philip M. Gollucci wrote: [PLEASE DROP GNATS from your replys] http://tinderbox-amd64.rws/index.php?action=list_buildportsbuild=8-CURRENT-RT38 should be http://tinderbox-amd64.riderway.com:8080/index.php?action=list_buildportsbuild=8-CURRENT-RT38 I saw everything is «success». When you think this ports is push into the ports-tree ? (for 7-Release). Lots of thanks for your work. 1) I need to figure a multi-instance patch first which I'm going to have to code from almost scratch for 3.8. 2) I need to test NOPORTDOCS, NPORTEXAMPLES, NOPORTDATA vars 3) I'm planing to install a field test of the port tonight/tomorrow at $work and make public through friday ish. 4) I need to deal with the post install make steps in a way different from previous rt ports so it stays package able. http://people.freebsd.org/~pgollucci/rt38.txt is a better link at this point to start with I'm come back for rt. Now I'm need to make a seconde install of rt before end of the mounth. I would like to known if you think before this date rt38 ports can be release ? I don't want push anyone because I can use rt36. All I would like to known is if it's good idea to wait. I prefer to not have to make a upgrade on rt. So if the www/rt38 going to be release soon I prefer to wait. Thanks for you work. Regards. -- Albert SHIH SIO batiment 15 Observatoire de Paris Meudon 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26 Heure local/Local time: Mer 5 nov 2008 14:47:12 CET ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Wacom driver
I have created a port of Bartosz Fabianowski's Wacom driver. Since nobody has stepped forward to commit it, I thought I'd inform this list, so that people can test it. http://www.freebsd.org/cgi/query-pr.cgi?pr=128547 Feedback is, of course, welcome. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wacom driver
Dominic Fandrey wrote: Gábor Kövesdán wrote: Dominic Fandrey escribió: I have created a port of Bartosz Fabianowski's Wacom driver. Since nobody has stepped forward to commit it, I thought I'd inform this list, so that people can test it. http://www.freebsd.org/cgi/query-pr.cgi?pr=128547 I suggest that you should consult with [EMAIL PROTECTED] He was going to port this driver himself but he hasn't got time so far. I've CC'd him because I don't think he is on the ports@ list because he is a doc committer. Well, I'm always willing to talk. However, I don't see much to be done here. The port is done, I keep close contact to Bartosz and I'm willing to maintain it. It's one of the few that actually installs a module into /boot/modules, something that should be enforced more thoroughly, in my opinion. Thanks to the ports Xorg magic I even don't have to take care of dependencies. Hello there, Thanks to Ping Cheng (maintainer of the original Linux driver), I already found and contacted Bartosz (at about middle of August), and I have tested some versions of his ported driver with my USB Wacom Bamboo. I asked him about an official FreeBSD port, but he replied he will do that himself (when it is time) :) I would be happy to see this driver in the Ports Collection, however I had serious problems with the latest version I tested (X crashed after a few minutes with Firefox and Gimp). It is a sorry, but I had to leave that configuration (6.3-STABLE on a desktop machine) behind (I had to move) and I switched to FreeBSD 7-PRERELEASE on a notebook meanwhile. I have not had time to test it again, though my Bamboo is next to my notebook :) (Therefore no physical limitations...) But if you need a committer for this port, I can offer you to look after your PRs, test and commit them (with some help from an experienced ports committer, of course). Cheers, :g ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
On Wed, 05 Nov 2008 03:13:33 -0600, Flex [EMAIL PROTECTED] wrote: I also agree with you Jeremy. devel/boost-devel makes no sense as it is a stable and not a development version.When there are so much ports that depend on devel/boost (as version 1.34) then I see two approaches to solve this. 1.) Try to find out if boost 1.37 is binary compatible with boost 1.34. If so, then we could update it to the actual version without breaking the ports depending on it, IMHO. I made this a question to the boost irc channel and got only the answer that this is doubtable so far. The binary compatible does not matter as it only forces us to wait until complete unfreeze. We can bump all of other ports to get rebuild. What about the API (source) compatible? It's more important than ABI (binary) compatible as we need to make sure others can build with newer boost. 2.) We should think of one or two alternative boost port(s) like devel/boost137 and devel/boost138. All depending ports must be made dependant to devel/boost137 then. Other ports also keep two ports with their (often major) release numbers and switch dependent ports back and forth to the right port release number. We don't need devel/boost137 either if all other ports can build with newer boost or easy to get others fix with newer boost. We should avoid two same exactly libraries in ports tree if they don't do the parallel installation (non-conflict) as possible unless no choice to do two or more. I'd prefer the second because there are less side effects and problems possible. Also please note that http://home.leo.org isn't accessible anymore. Hopefully someone, preferrably Alexander, has the 1.35 patch from Simon to check whether it's easy to bump the port to 1.37 easily. I also agree to send a PR. Yeah, two people have told me about that URL is dead. Too bad, I don't have this file anymore. Cheers, Mezz /Flex -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Boost 1.37 released!
On 2008-Nov-05 09:52:12 -0600, Jeremy Messenger [EMAIL PROTECTED] wrote: On Wed, 05 Nov 2008 03:13:33 -0600, Flex [EMAIL PROTECTED] wrote: Also please note that http://home.leo.org isn't accessible anymore. Yeah, two people have told me about that URL is dead. Too bad, I don't have this file anymore. Depending on how long it was up, it might have been grabbed by the Internet Archive Wayback Machine. It's not there right now but the FAQ says it generally takes 6 months or more for pages to appear. That URL looks like the member's area of an ISP - it's also possible that LEO just renamed (rather than removed) the site. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpQ0zEF1sgAm.pgp Description: PGP signature
Problems building ports - Error code 2 when attempting to cd
All, I have a strange port problem that I am trying to figure out. Hopefully someone can shed a light on what is happening here: === rrdtool-1.2.26_1 depends on file: /usr/local/bin/libtool - found (but building it anyway) ===Verifying install for /usr/local/bin/libtool in /usr/ports/devel/libtool15 === Returning to build of rrdtool-1.2.26_1 === rrdtool-1.2.26_1 depends on shared library: freetype.9 - found (but building it anyway) ===Verifying install for freetype.9 in /usr/ports/print/freetype2 cd: can't cd to /usr/ports/print/freetype2/work/freetype-2.3.7 *** Error code 2 1 error *** Error code 2 1 error But as you can see here, it does exist: freebsd-nexus-computers# ls /usr/ports/print/freetype2/work/freetype-2.3.7 ChangeLog ChangeLog.22Makefileautogen.sh devel modules.cfg version.sed ChangeLog.20Jamfile README builds docs objsvms_make.com ChangeLog.21JamrulesREADME.CVS configure include src Does anyone have any idea what is happening here? This is happening randomly to a number of port builds and I am stumped. Thanks, Scott PS: please CC me on any replies, I am not subscribed to this particular list ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wacom driver
On Wed, Nov 5, 2008 at 11:22 AM, Dominic Fandrey [EMAIL PROTECTED] wrote: Hello, I have created a port of Bartosz Fabianowski's Wacom driver. Since nobody has stepped forward to commit it, I thought I'd inform this list, so that people can test it. http://www.freebsd.org/cgi/query-pr.cgi?pr=128547 I tried compiling it my system but building the port fails for me. Two diffs are attached, one for the Makefile of the port itself and one for uwacom.c in the code of Bartosz Fabianowski. My system is running a recent current btw: # uname -a FreeBSD Tablet.lan 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Tue Nov 4 15:27:47 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TABLET amd64 makefile.diff : The Makefile of the port tries to create a link to the linuxwacom archive in the work-dir of the port. However, this archive is located in /usr/ports/distfiles/xorg/driver/ in stead of just /usr/ports/distfiles/ (or is this something specific to current?) uwacom.diff: uwacom.c is missing the include sys/clist.h Maybe this was indirectly included in a different header file in 6.x or 7.0? After these changes the compile of uwacom.c still fails with: = cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c uwacom.c cc1: warnings being treated as errors uwacom.c: In function 'uwacom_init': uwacom.c:1072: warning: left shift count = width of type *** Error code 1 Stop in /usr/ports/x11-drivers/xf86-input-wacom/work/uwacom. *** Error code 1 = Removing -Werror from the compile step silently ignores this warning, but I guess that's not the right way to deal with this :) I'm not familiar with the code at all and don't really know how to solve this, but maybe you do. Can't verify if it works though, I'm using it on a Tablet PC (Fujitsu T4220) for which the wacom device should show up as a serial device. (However, I'm still having some problems with that though) As a sidenote. The tablets which use a serial port (e.g. most tabletPCs according to the linuxwacom documentation) don't need the the usb-part if I'm correct. So maybe it would be a good idea to split the port into two parts? One just for the linuxwacom codebase, and one for the kernel module? (which then depends on the linuxwacom port) Kind regards, Bruno makefile.diff Description: Binary data uwacom.diff Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Wacom driver
Hello, On Wed, Nov 5, 2008 at 8:34 PM, bomberboy [EMAIL PROTECTED] wrote: My system is running a recent current btw: # uname -a FreeBSD Tablet.lan 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Tue Nov 4 15:27:47 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TABLET amd64 Under 7.0-stable / i386: [EMAIL PROTECTED] uname -a FreeBSD kg-work2.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #2: Sun Oct 19 19:29:06 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SX270 i386 makefile.diff : The port compiles fine here with this diff. No need for the other diff. My Wacom CTF-420 is detected: [EMAIL PROTECTED] usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: low speed, power 40 mA, config 1, CTF-420 V2.0-0(0x0062), WACOM(0x056a), rev 2.00 from /var/log/messages: Nov 5 22:43:13 kg-work2 root: Unknown USB device: vendor 0x056a product 0x0062 bus uhub0 Nov 5 22:43:13 kg-work2 kernel: uwacom0: WACOM CTF-420 V2.0-0, class 0/0, rev 1.10/2.00, addr 2 on uhub0 It works too (after I restated X), at least as a mouse (I don't know how to test the other functions). uwacom.diff: uwacom.c is missing the include sys/clist.h Maybe this was indirectly included in a different header file in 6.x or 7.0? I do not know, I ony know that I didn't need this on my machine. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
On pkg_trans
Hi, I'll probably have some time in the next few days to work on pkg_trans again, but first I'd like to get some input on the whole thing. The last time I talked about it I've made code available but I've received no feedback. More information on pkg_trans can be found in the list archives or on these pages: http://wiki.freebsd.org/IvanVoras/PkgTransProposal http://ivoras.sharanet.org/blog/tree/2008-10-13.addition-to-freebsds-package-infrastructure--pkg_trans.html Those pages also carry links to the code. I'm not a ports committer and I don't want to tell people who are how to work on their project but I think pkg_trans is important enough that it should require a policy decision - if it's accepted, pkg_trans should go into the base system. I know that there are utilities than can do some or all of what I've planned for pkg_trans but one important point of pkg_trans is that it should be integrated into the regular base package infrastructure, not requiring external utilities, runtimes or libraries. Some implementation notes: * I've avoided changes to the base utilities. A separate utility, pkg_trans, is called by the transaction-aware utilities * Client-side utilities are added to the pkg_install library (lib.h, etc.) * Transaction records are kept as text files. I think it would have been significantly better if sqlite was used but there was great opposition to importing sqlite into the base system the last time I brought it up so this is the last mention of it (in context of pkg_trans :) ) * If it's accepted, I'll maintain this addition to the utilities (of course, everyone's invited to contribute). I'll also be a regular user of these features - I created pkg_trans because I want the functionality on my systems. * For the pkg_trans to be effective, it requires slight modifications to the ports Makefile infrastructure (basically, the install and deinstall targets should be aware of transactions) and external ports utilities (like portupgrade), which I can't do myself. If there's interest in finishing pkg_trans, now's the time to discuss it :) signature.asc Description: OpenPGP digital signature
Re: Problems building ports - Error code 2 when attempting to cd
On Wed, Nov 05, 2008 at 03:49:29PM -0400, Scott Ullrich wrote: All, I have a strange port problem that I am trying to figure out. Hopefully someone can shed a light on what is happening here: === rrdtool-1.2.26_1 depends on file: /usr/local/bin/libtool - found (but building it anyway) ===Verifying install for /usr/local/bin/libtool in /usr/ports/devel/libtool15 === Returning to build of rrdtool-1.2.26_1 === rrdtool-1.2.26_1 depends on shared library: freetype.9 - found (but building it anyway) ===Verifying install for freetype.9 in /usr/ports/print/freetype2 cd: can't cd to /usr/ports/print/freetype2/work/freetype-2.3.7 *** Error code 2 1 error *** Error code 2 1 error But as you can see here, it does exist: freebsd-nexus-computers# ls /usr/ports/print/freetype2/work/freetype-2.3.7 ChangeLog ChangeLog.22Makefileautogen.sh devel modules.cfg version.sed ChangeLog.20 Jamfile README builds docs objsvms_make.com ChangeLog.21 JamrulesREADME.CVS configure include src Does anyone have any idea what is happening here? This is happening randomly to a number of port builds and I am stumped. Please provide the output from the following commands: mount ls -ld / /usr /usr/ports /usr/ports/print /usr/ports/print/freetype2 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems building ports - Error code 2 when attempting to cd
On Wed, Nov 05, 2008 at 09:04:18PM -0500, Scott Ullrich wrote: On Wed, Nov 5, 2008 at 9:01 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: Please provide the output from the following commands: mount ls -ld / /usr /usr/ports /usr/ports/print /usr/ports/print/freetype2 Here is mount: /dev/da0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/da0s1d on /usr (ufs, local, soft-updates) devfs on /usr/jails/sullrich/dev (devfs, local) fdescfs on /usr/jails/sullrich/dev/fd (fdescfs) procfs on /usr/jails/sullrich/proc (procfs, local) devfs on /usr/jails/ermal/dev (devfs, local) fdescfs on /usr/jails/ermal/dev/fd (fdescfs) procfs on /usr/jails/ermal/proc (procfs, local) devfs on /usr/jails/billm/dev (devfs, local) fdescfs on /usr/jails/billm/dev/fd (fdescfs) procfs on /usr/jails/billm/proc (procfs, local) devfs on /usr/jails/ondemand/dev (devfs, local) fdescfs on /usr/jails/ondemand/dev/fd (fdescfs) procfs on /usr/jails/ondemand/proc (procfs, local) devfs on /usr/local/pfsense-fs/dev (devfs, local) (Note that it is a jail host and this build was running within a jail) freebsd-nexus-computers# ls -ld / /usr /usr/ports /usr/ports/print /usr/ports/print/freetype2 drwxr-xr-x 20 root wheel 512 Nov 2 18:47 / drwxr-xr-x 18 root wheel 512 Nov 5 14:20 /usr drwxr-xr-x 70 root wheel 1536 Nov 5 15:15 /usr/ports drwxr-xr-x 331 root wheel 7168 Nov 5 15:16 /usr/ports/print drwxr-xr-x3 root wheel 512 Nov 5 15:16 /usr/ports/print/freetype2 They all exist. The error message is really strange. Anything else you can think to check? Does the problem happen outside of the jail? Other than that, I have no ideas. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems building ports - Error code 2 when attempting to cd
On Wed, Nov 5, 2008 at 9:09 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: Does the problem happen outside of the jail? Unfortunately it does from time to time even with -j1 Other than that, I have no ideas. Thanks for trying. This is one of those situations where I am out of ideas as well. Scott ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems building ports - Error code 2 when attempting to cd
Sorry, forgot reply-all. On Wed, Nov 5, 2008 at 10:49 PM, Diane Bruce [EMAIL PROTECTED] wrote: Look for this variable set somewhere. ALWAYS_BUILD_DEPENDS I enabled this in a last ditch effort to get around the problem. It instructs dependencies to rebuild even if the ports tree thinks it is not necessary. From what I gather it only adds additional time when rebuilding the port. This message but building it anyway is odd. looking in /usr/ports/Mk , I'd like to know why ALWAYS_BUILD_DEPENDS is set. That can't be right. What are you typing to do the make? The problem occurs regardless of if this is defined or not. The script being used is: http://cvs.pfsense.org/cgi-bin/cvsweb.cgi/tools/pfPorts/Makefile.RELENG_1?rev=1.66;content-type=text%2Fplain Don't let the filename fool you, its a simple shell script that was originally a sub-port make file quite a while back and we have not repo moved the file to reflect its new purpose. I did notice something else odd, even after the cd command fails, the port starts back over and somehow it finishes building which seems a bit strange (regardless if ALWAYS_BUILD_DEPENDS is defined). Scott ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems building ports - Error code 2 when attempting to cd
On Wed, Nov 05, 2008 at 09:04:18PM -0500, Scott Ullrich wrote: ... Anything else you can think to check? Look for this variable set somewhere. ALWAYS_BUILD_DEPENDS === rrdtool-1.2.26_1 depends on shared library: freetype.9 - found (but building it anyway) This message but building it anyway is odd. looking in /usr/ports/Mk , I'd like to know why ALWAYS_BUILD_DEPENDS is set. That can't be right. What are you typing to do the make? -- - [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.db.net/~db ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
port request - listadmin (mailman admin utility)
I don't know if this is exactly the right place to ask, but I'd like to request a port. Previously, on debian, I administered a number of mailman lists using a CLI tool listadmin. After migrating my servers to FreeBSD 7 I'm unable to find that port. http://freshmeat.net/projects/listadmin/ Thank You, Christer pgpLsE1ICwsbK.pgp Description: PGP signature
Re: Problems building ports - Error code 2 when attempting to cd
Scott Ullrich [EMAIL PROTECTED] writes: On Wed, Nov 5, 2008 at 9:09 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: Does the problem happen outside of the jail? Unfortunately it does from time to time even with -j1 According to make(1) -j1 is not the same as if -j is not defined. I'd try either remove -j1 or add -B option: - −B Try to be backwards compatible by executing a single shell per command and by executing the commands to make the sources of a dependency line in sequence. This is turned on by default unless −j is used. −j max_jobs Specify the maximum number of jobs that make may have running at any one time. Turns compatibility mode off, unless the −B flag is also specified. - HTH WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
