How-to maximize your profit from China
[1][logo.gif] [2][banner.gif] [3]WELCOME TO GOGOEC.COM This is your best opportunity to directly access the Chinese electronics market ! [4][tittle_about%20us.gif] [5]GOGOEC is a HONG KONG trading and wholesale company based in Shenzhen, China right next to Hong Kong. We buy exclusively from Chinese manufacturers who produce Consumer Electronics, gadgets, and PC accessories, garments and accessories. Everything we buy and sell is made in China and now you can buy these products direct from China, at wholesale prices. We offer you a wide-selection of products. This is your best opportunity to directly access the Chinese electronics market How experienced and reputable is your company in this field.. [about%20us_pic.gif] [hot%20products_title.gif] [6][hot%20products_pic1.gif] [hot%20products_line.gif] [7][hot%20products_pic2.gif] [8]BRAND NEW 100%Origina Made in Finlan Brand New NOKIA 8800 ... Price:USD: 488 / Pieces [9]Brand New Car DVD Player with Built-in TV Receiver!best price Price: USD: 141/ Pieces [10][hot%20products_pic3.gif] [hot%20products_line.gif] [11][hot%20products_pic4.gif] [12]free shipping!COOG Hoodies size:xl~xxl~xxxl Price:USD 36/Pieces [13]100% Brand New Prada Men shoes Come with new Price:USD 33 /Pieces [hot%20products_pic.gif] [autumn%20time_title.gif] [14][autumn%20time_pic1.gif] [15][autumn%20time_pic2.gif] [16][autumn%20time_pic3.gif] [17][autumn%20time_pic4.gif] [18][autumn%20time_pic5.gif] [19][autumn%20time_pic6.gif] [20][autumn%20time_pic7.gif] [21][autumn%20time_pic8.gif] [22][autumn%20time_pic9.gif] [23][autumn%20time_pic10.gif] [24][autumn%20time_pic11.gif] [25][autumn%20time_pic12.gif] [26][autumn%20time_pic13.gif] [27][autumn%20time_pic14.gif] [28][autumn%20time_pic15.gif] [autumn%20time_pic.gif] [29][bottom_logo.gif] [30][bottom_pic1.gif] [31]About US | [32]Contact Us|[33]Security & Privacy| Site Map |[34]Help Copyright � 1995-2006 GoGoEc Inc. All Rights Reserved.Designated trademarks and brands are the property of their respective owners. [flosensing?z=de40PCjxu0DQM0Bn] References Visible links 1. http://www.gogoec.com/ 2. http://www.gogoec.com/ 3. http://www.gogoec.com/ 4. http://www.gogoec.com/help/CompanyInfo.asp 5. http://www.gogoec.com/help/CompanyInfo.asp 6. http://www.gogoec.com/productdisplay.asp?id=2b2dcc32d6327985 7. http://www.gogoec.com/productdisplay.asp?id=6f764367fc7806cb 8. http://www.gogoec.com/productdisplay.asp?id=6f764367fc7806cb 9. http://www.gogoec.com/productdisplay.asp?id=6f764367fc7806cb 10. http://www.gogoec.com/productdisplay.asp?id=566e9636571bfb92 11. http://www.gogoec.com/productdisplay.asp?id=ef6a5e2e8aca784c 12. http://www.gogoec.com/productdisplay.asp?id=566e9636571bfb92 13. http://www.gogoec.com/productdisplay.asp?id=ef6a5e2e8aca784c 14. http://www.gogoec.com/clothes.Asp 15. http://www.gogoec.com/clothes.Asp 16. http://www.gogoec.com/clothes.Asp 17. http://www.gogoec.com/clothes.Asp 18. http://www.gogoec.com/clothes.Asp 19. http://www.gogoec.com/clothes.Asp 20. http://www.gogoec.com/clothes.Asp 21. http://www.gogoec.com/ConsumerElectronics.Asp 22. http://www.gogoec.com/shoes.html 23. http://www.gogoec.com/ConsumerElectronics.Asp 24. http://www.gogoec.com/ConsumerElectronics.Asp 25. http://www.gogoec.com/clothes.Asp 26. http://www.gogoec.com/ConsumerElectronics.Asp 27. http://www.gogoec.com/clothes.Asp 28. http://www.gogoec.com/mobilephone.Asp 29. http://www.gogoec.com/shoes.html 30. http://www.gogoec.com/shoes.html 31. http://www.gogoec.com/help/CompanyInfo.asp 32. http://www.gogoec.com/help/ContactUs.asp 33. http://www.gogoec.com/help/GOGOECPrivacyPolicy.asp 34. http://www.gogoec.com/help/CanItrustGOGOEC.asp Hidden links: 35. http://www.gogoec.com/EDM/EDM200710170907/productdisplay.asp?id=6f764367fc7806cb 36. http://www.gogoec.com/html/aboutus/Security%20&%20Privacy.asp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RE : asterisk-addons build problem on 6.2/i386
To check myself I updated ports again and run portupgrade -NR net/asterisk-addons - same error. tracy musaza пишет: Can U update ports tree then reinstall asterisk? I see there is some probl with some dependancies: asterisk-addons cheers!! */"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>/* a écrit : Hi to all! I have problem building net/asterisk-addons on two FreeBSD 6.2/i386 machines. src/chan_h323.c:3249: error: dereferencing pointer to incomplete type src/chan_h323.c:3250: error: dereferencing pointer to incomplete type src/chan_h323.c:3251: error: dereferencing pointer to incomplete type src/chan_h323.c:3220: error: storage size of `null_frame' isn't known src/chan_h323.c: In function `ooh323_convert_hangupcause_asteriskToH323': src/chan_h323.c:3271: error: `AST_CAUSE_CALL_REJECTED' undeclared (first use in this function) src/chan_h323.c:3273: error: `AST_CAUSE_UNALLOCATED' undeclared (first use in this function) src/chan_h323.c:3275: error: `AST_CAUSE_BUSY' undeclared (first use in this function) src/chan_h323.c:3277: error: `AST_CAUSE_BEARERCAPABILITY_NOTAVAIL' undeclared (first use in this function) src/chan_h323.c:3279: error: `AST_CAUSE_CONGESTION' undeclared (first use in this function) src/chan_h323.c:3281: error: `AST_CAUSE_NO_ANSWER' undeclared (first use in this function) src/chan_h323.c:3283: error: `AST_CAUSE_NORMAL' undeclared (first use in this function) src/chan_h323.c:3285: error: `AST_CAUSE_FAILURE' undeclared (first use in this function) src/chan_h323.c: In function `ooh323_convert_hangupcause_h323ToAsterisk': src/chan_h323.c:3299: error: `AST_CAUSE_CALL_REJECTED' undeclared (first use in this function) src/chan_h323.c:3301: error: `AST_CAUSE_UNALLOCATED' undeclared (first use in this function) src/chan_h323.c:3304: error: `AST_CAUSE_BUSY' undeclared (first use in this function) src/chan_h323.c:3306: error: `AST_CAUSE_BEARERCAPABILITY_NOTAVAIL' undeclared (first use in this function) src/chan_h323.c:3309: error: `AST_CAUSE_CONGESTION' undeclared (first use in this function) src/chan_h323.c:3311: error: `AST_CAUSE_NO_ANSWER' undeclared (first use in this function) src/chan_h323.c:3315: error: `AST_CAUSE_FAILURE' undeclared (first use in this function) src/chan_h323.c:3317: error: `AST_CAUSE_NORMAL' undeclared (first use in this function) src/chan_h323.c: At top level: src/chan_h323.c:3330: error: syntax error before string constant src/chan_h323.c:3330: warning: data definition has no type or storage class src/chan_h323.c:67: error: storage size of `ooh323_tech' isn't known src/chan_h323.c:86: error: storage size of `ooh323_rtp' isn't known src/chan_h323.c:206: error: storage size of `gCallerID' isn't known src/chan_h323.c:209: error: storage size of `gPrefs' isn't known src/chan_h323.c:222: error: storage size of `gContext' isn't known src/chan_h323.c:2427: error: storage size of `cli_debug' isn't known src/chan_h323.c:2434: error: storage size of `cli_no_debug' isn't known src/chan_h323.c:2441: error: storage size of `cli_show_users' isn't known src/chan_h323.c:2448: error: storage size of `cli_show_user' isn't known src/chan_h323.c:2455: error: storage size of `cli_show_peers' isn't known src/chan_h323.c:2462: error: storage size of `cli_show_peer' isn't known src/chan_h323.c:2465: error: storage size of `cli_show_config' isn't known gmake[3]: *** [chan_h323.lo] Ошибка 1 gmake[3]: Leaving directory `/usr/ports/net/asterisk-addons/work/asterisk-addons-1.4.2/asterisk-ooh323c' gmake[2]: *** [all] Ошибка 2 gmake[2]: Leaving directory `/usr/ports/net/asterisk-addons/work/asterisk-addons-1.4.2/asterisk-ooh323c' gmake[1]: *** [chan_ooh323.so] Ошибка 2 rm app_saycountpl.o gmake[1]: Leaving directory `/usr/ports/net/asterisk-addons/work/asterisk-addons-1.4.2' gmake: *** [all] Ошибка 2 *** Error code 2 Stop in /usr/ports/net/asterisk-addons. *** Error code 1 Stop in /usr/ports/net/asterisk-addons. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.42772.0 env make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! net/asterisk-addons (missing header) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed gw# uname -a FreeBSD gw 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 -- С уважением, Савчук Ð¢Ð°Ñ€Ð°Ñ ÐžÐžÐž "Ðлантек" : ÐутÑорÑинг ИТ, WEB-разработка http://www.elantech.ru +7 (495) 589 68 81 +7 (926) 779 07 05 ___ freebsd-ports@freebsd.
[update-request] please help to maintiners
Hello, all! this is a unsupportet structure code: == .if !defined(WITH_SERVER) PLIST_SUB+= SERVER="@comment " .if defined(WITH_MYSQL) || !defined(WITHOUT_PGSQL) || !defined(WITHOUT_SQLITE) || !defined(WITHOUT_ODBC) IGNORE= is useless database support without a SERVER. Please (re)run 'make config' and choose SERVER with database .endif .else CONFIGURE_ARGS+=--with-server PLIST_SUB+= SERVER="" .if defined(WITHOUT_MYSQL) && !defined(WITH_PGSQL) && !defined(WITH_SQLITE) && !defined(WITH_ODBC) IGNORE= is useless without a database. Please (re)run 'make config' and choose one of PGSQL and MYSQL .else USE_RC_SUBR+= netxmsd .if defined(WITH_AGENT) PLIST_SUB+= AGENT="@comment " .else USE_RC_SUBR+= netxmsd nxagentd .endif .endif .endif == plaese add support for help to maintiners it comfortably /Vladimir Ermakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
graphics/OpenEXR fails
I'm getting failures when trying to upgrade OpenEXR. /usr/bin/ld: warning: libHalf.so.4, needed by /usr/local/lib/libIlmImf.so, may conflict with libHalf.so.6 /usr/bin/ld: warning: libIex.so.4, needed by /usr/local/lib/libIlmImf.so, may conflict with libIex.so.6 /usr/bin/ld: warning: libIlmThread.so.4, needed by /usr/local/lib/libIlmImf.so, may conflict with libIlmThread.so.6 Would it work to delete the old libs and then symlink from the newer ones? -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
graphics/OpenEXR fails
Paul Schmehl writes: > I'm getting failures when trying to upgrade OpenEXR. /usr/ports/UPDATING Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/OpenEXR fails
Paul Schmehl wrote: > I'm getting failures when trying to upgrade OpenEXR. > > /usr/bin/ld: warning: libHalf.so.4, needed by > /usr/local/lib/libIlmImf.so, may conflict with libHalf.so.6 > /usr/bin/ld: warning: libIex.so.4, needed by > /usr/local/lib/libIlmImf.so, may conflict with libIex.so.6 > /usr/bin/ld: warning: libIlmThread.so.4, needed by > /usr/local/lib/libIlmImf.so, may conflict with libIlmThread.so.6 > > Would it work to delete the old libs and then symlink from the newer ones? > a) Don't symlink libraries, make entries in libmap.conf. b) The best solution would be to rebuild the port /usr/local/lib/libIlmImf.so belongs to. I suppose lib*.so.4 are in /usr/local/lib/compat/pkg, because there normally aren't several versions of one library available. I'll soon release a script that lists packages that link against libraries in /usr/local/lib/compat or are linked with missing libraries in a sysutils/bsdadminscripts release. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/OpenEXR fails
On 10/18/07, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: > Paul Schmehl wrote: > > I'm getting failures when trying to upgrade OpenEXR. > > > > /usr/bin/ld: warning: libHalf.so.4, needed by > > /usr/local/lib/libIlmImf.so, may conflict with libHalf.so.6 > > /usr/bin/ld: warning: libIex.so.4, needed by > > /usr/local/lib/libIlmImf.so, may conflict with libIex.so.6 > > /usr/bin/ld: warning: libIlmThread.so.4, needed by > > /usr/local/lib/libIlmImf.so, may conflict with libIlmThread.so.6 > > > > Would it work to delete the old libs and then symlink from the newer ones? > > > > a) Don't symlink libraries, make entries in libmap.conf. > > b) The best solution would be to rebuild the port /usr/local/lib/libIlmImf.so > belongs to. I suppose lib*.so.4 are in /usr/local/lib/compat/pkg, because > there normally aren't several versions of one library available. > > I'll soon release a script that lists packages that link against libraries in > /usr/local/lib/compat or are linked with missing libraries in a > sysutils/bsdadminscripts release. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > I had this same trouble last week and it was fixed by following the instructions in /usr/ports/UPDATING ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/OpenEXR fails
On Thu, 18 Oct 2007 12:02:31 -0500 Paul Schmehl <[EMAIL PROTECTED]> wrote: |Would it work to delete the old libs and then symlink from the newer |ones? Please read ports/UPDATING - Martin -- Martin Wilke| irc.unixfreunde.de #bsd [EMAIL PROTECTED] | [EMAIL PROTECTED] FreeBSD Committer | Power to Serve signature.asc Description: PGP signature
Re: graphics/OpenEXR fails
--On Thursday, October 18, 2007 13:11:44 -0400 Robert Huff <[EMAIL PROTECTED]> wrote: Paul Schmehl writes: I'm getting failures when trying to upgrade OpenEXR. /usr/ports/UPDATING BTDT. Took a make distclean, then make install, to solve the problem. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The scandalous status of linux-flashplugin9
> > There was a report on -current a while ago that a preliminary patch > > to fix the non-threadsafeness of mmap(2) MAP_FIXED also makes flash9 work, > > > > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075968.html I wrote that and I was wrong... it doesnt seem to fix the flash9 problem for me. > > a fix for that seems to have been committed (kib 2007-08-20) and also > > mfc'd to RELENG_6 by now (kib 2007-09-09), so, can anyone running either > > verify that flash9 still crashes for them? > > Ok I now have a sucess story for RELENG_7 using linux-base-fc4 > (hi wallshot! :) - he couldnt get it to work with linux-base-f7), and > I myself (he tested too) couldnt get it working by merging the RELENG_6 > commit to 6.2, or by testing a RELENG_6 kernel and linux.ko on 6.2 userland. > So it looks like you need 7, and there's still work to be done for the > linux 2.6 emulation there also. I dont understand what you say.. you have working flash9 on RELENG_7/fc4? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The scandalous status of linux-flashplugin9
[adding -emulation to Cc, just in case...] On Wed, Oct 10, 2007 at 09:40:55PM +0200, I wrote: > In article <[EMAIL PROTECTED]> you write: > >Quoting John Reynolds <[EMAIL PROTECTED]> (Mon, 8 Oct 2007 08:10:11 -0700): > > > >> > >> [ On Monday, October 8, Scot Hetzel wrote: ] > >> > The port is not broken as the flash9 port is not compiled, it just > >> > installs the linux flash9 binary. What is broken is the linux > >> > emulation on FreeBSD < 7. Work is underway to improve the linux > >> > emulation in -CURRENT. > >> > > >> > I agree the port should be marked broken for OSVERSION < 7000xx, and > >> > compat.linux.osrelease = 2.4.2, as the flash9 plugin may require > >> > 2.6.16 linux emulation. > >> > >> Is there a handbook or wiki entry which would point one to the procedure > >> for > >> "properly" moving from 2.4.2 to 2.6.16 emulation under -current? I believe > >> I > >> saw some posts that 2.6.x would not be default for 7.0-RELEASE for whatever > >> technical reason. > > > >% grep linux /etc/sysctl.conf > >compat.linux.osrelease=2.6.16 > > > >Be warned, you may run into bugs (2.6 emulation has not as much > >widespread testing as 2.4). If you stumble upon problems have a look at > >the archive of emulation@ and search for your problem there. If you can > >not find it, tell emulation@ about your problem. Be prepared to do some > >guided debugging. > > > >> Can anybody report success on -current with 2.6.16 emulation with the > >> flash9 > >> plugin? > > > >No, there are bugs we didn't manage to track down yet (partly because of > >lack of time, partly because of the closed source nature of flash9,). > >If someone wants to help to track this down: install dtrace (I don't > >know where install instructions are; it's back from hibernation just > >recently), run flash9 and try to get a backtrace of a crash with > >dtrace. If someone manages to do this, post the backtrace to [EMAIL > >PROTECTED] > > > >Bye, > >Alexander. > > There was a report on -current a while ago that a preliminary patch > to fix the non-threadsafeness of mmap(2) MAP_FIXED also makes flash9 work, > > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075968.html > a fix for that seems to have been committed (kib 2007-08-20) and also > mfc'd to RELENG_6 by now (kib 2007-09-09), so, can anyone running either > verify that flash9 still crashes for them? Ok I now have a sucess story for RELENG_7 using linux-base-fc4 (hi wallshot! :) - he couldnt get it to work with linux-base-f7), and I myself (he tested too) couldnt get it working by merging the RELENG_6 commit to 6.2, or by testing a RELENG_6 kernel and linux.ko on 6.2 userland. So it looks like you need 7, and there's still work to be done for the linux 2.6 emulation there also. Oh, here's the patch I used on 6.2: http://people.freebsd.org/~nox/mmap-6.2.patch meged from this commit: kib 2007-09-09 04:41:24 UTC FreeBSD src repository Modified files:(Branch: RELENG_6) sys/vm vm_map.c vm_map.h vm_mmap.c Log: MFC rev. 1.387 of src/sys/vm/vm_map.c rev. 1.120 of src/sys/vm/vm_map.h rev. 1.213 of src/sys/vm/vm_mmap.c Do not drop vm_map lock between doing vm_map_remove() and vm_map_insert(). For this, introduce vm_map_fixed() that does that for MAP_FIXED case. Tested by: Marc G. Fournier Revision ChangesPath 1.366.2.6 +35 -16src/sys/vm/vm_map.c 1.117.2.2 +1 -0 src/sys/vm/vm_map.h 1.200.2.4 +4 -2 src/sys/vm/vm_mmap.c HTH, Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The scandalous status of linux-flashplugin9
On 10/18/07, Roman Divacky <[EMAIL PROTECTED]> wrote: > > > There was a report on -current a while ago that a preliminary patch > > > to fix the non-threadsafeness of mmap(2) MAP_FIXED also makes flash9 work, > > > > > > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075968.html > > I wrote that and I was wrong... it doesnt seem to fix the flash9 problem for > me. > > > > a fix for that seems to have been committed (kib 2007-08-20) and also > > > mfc'd to RELENG_6 by now (kib 2007-09-09), so, can anyone running either > > > verify that flash9 still crashes for them? > > > > Ok I now have a sucess story for RELENG_7 using linux-base-fc4 > > (hi wallshot! :) - he couldnt get it to work with linux-base-f7), and > > I myself (he tested too) couldnt get it working by merging the RELENG_6 > > commit to 6.2, or by testing a RELENG_6 kernel and linux.ko on 6.2 userland. > > So it looks like you need 7, and there's still work to be done for the > > linux 2.6 emulation there also. > I too am confused, if you have flash 9 working in firefox on RELENG_7 please give us a detailed how to there are just a TON of people looking for this. I have 5 systems I would test it out on right now, 2 of them are teenager computers so they would get a workout on youtube , among other sites that require flash 8 :) Sam Fourman Jr. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: The scandalous status of linux-flashplugin9
On Thu, Oct 18, 2007 at 09:51:44PM +0200, I wrote: > > There was a report on -current a while ago that a preliminary patch > > to fix the non-threadsafeness of mmap(2) MAP_FIXED also makes flash9 work, > > > > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075968.html > > a fix for that seems to have been committed (kib 2007-08-20) and also > > mfc'd to RELENG_6 by now (kib 2007-09-09), so, can anyone running either > > verify that flash9 still crashes for them? > > Ok I now have a sucess story for RELENG_7 using linux-base-fc4 > (hi wallshot! :) - he couldnt get it to work with linux-base-f7), and > I myself (he tested too) couldnt get it working by merging the RELENG_6 > commit to 6.2, or by testing a RELENG_6 kernel and linux.ko on 6.2 userland. > So it looks like you need 7, and there's still work to be done for the > linux 2.6 emulation there also. nvm, false alarm: [...] it worked for me for hours and hours then crapped out :( Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
parallel ports build
With most modern systems having 2+ cores, I was wondering if the ports
system could make use of more than one of them. I briefly searched the
web and list archives and found several short discussions and the
following page (cced author markus@):
http://www.brueffer.de/parallel_ports_build.html
The bsd.port.mk patch on that page is dated March 2004 (!) but looks
pretty simple. A port must set "SUPPORTS_PARALLEL_BUILD=yes" to allow a
parallel build. If it does, the BUILD_JOBS knob is used (either read from
/etc/make.conf, env, or defaults to 0) and "-j${BUILD_JOBS}" is passed to
make. As a bonus, the patch includes CC/CXX wrapper support for
ccache/distcc/etc.
Given that not all ports successfully build in parallel, the opt-in
approach seems reasonable. It allows port maintainers to test their ports
and update them if everything works well. Even a simple pass through the
ports tree focusing on the heavy-hitters (X, KDE, Gnome, Apache, PHP,
MySQL, Postgres, OpenOffice, etc.) and their dependencies could make a
significant dent in build time. This would be most evident for new
installs and upgrades where you are basically starting from scratch.
I am far from an expert in this area so I wanted to see what others
thought. Is this a good approach or is there a better one?
-Jon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
