Re: How to upgrade perl 5.8 to 5.10?
Boris Kochergin wrote: Helmut Schneider wrote: Michal Varga wrote: # pkg_info | wc -l 457 # And this machine is even my package-building station! Anyway, portupgrade -af took 45 minutes. g Well, it's a dedicated blade after all :) And those 8 cores seem pretty nasty, I'm envious. Well, afaik I even cannot use more than one CPU when building ports. There were plans/rumors that this would change. Does anyone know more about it? It has happened: http://lists.freebsd.org/pipermail/freebsd-ports/2009-March/053736.html That'd explain a lot :) ___ 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: How to upgrade perl 5.8 to 5.10?
On Wed, Jan 20, 2010 at 08:03:32PM +0100, Michal Varga wrote: Well, it's a dedicated blade after all :) And those 8 cores seem pretty nasty, I'm envious. Well, afaik I even cannot use more than one CPU when building ports. There were plans/rumors that this would change. Does anyone know more about it? Sure you can, as Boris (below) linked, this happened long time ago, especially: You don't need to do anything to enable the new feature. Whitelisted ports will automatically make use of all processors available in your computer. Most large ports I have seen (and use) luckily take advantage of all available processors during build (which completely sucks for desktop systems, but then, you normally shouldn't do that on a station where you try to work, so I'm fine with that). There's no way you'd be able to build 450 ports in 45 minutes if you were using only one CPU/core. It has happened: http://lists.freebsd.org/pipermail/freebsd-ports/2009-March/053736.html I believe *dependencies* of a port will be compiled using one process (and thus CPU) at a time, however. Interesting, are you sure this really happens? At least I understand you mean that - let's say - when i choose to compile, i.e. www/webkit directly, it will use all available processors (which it does, all the time), but when I try to compile, say, www/epiphany, which pulls www/webkit as a dependency, it will get built without MAKE_JOBS_SAFE, locked to a single processor? I can test in a short while if that's really the way, just asking, if I got you right.. No. Only one port is built at a time but if that port is MAKE_JOBS_SAFE it will build in parallel. -- 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
How to upgrade perl 5.8 to 5.10?
Hi, /usr/ports/UPDATING says: portupgrade -o lang/perl5.10 -f perl-5.8.\* # BATCH=YES portupgrade -o lang/perl5.10 -f perl-threaded-5.8.\* --- Upgrading 'perl-threaded-5.8.9_3' to 'perl-threaded-5.10.1' (lang/perl5.10) --- Building '/usr/ports/lang/perl5.10' with make flags: -DWITH_THREADS === Cleaning for perl-threaded-5.10.1 === perl-threaded-5.10.1 conflicts with installed package(s): perl-threaded-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/lang/perl5.10. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100120-80814-1ge6b2r-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=perl-threaded-5.8.9_3 UPGRADE_PORT_VER=5.8.9_3 make -DWITH_THREADS ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! lang/perl5.10 (perl-threaded-5.8.9_3) (unknown build error) # Currently the only solution seems to remove perl.5.8 which as a result deletes all dependencies which requires *all* ports to be reinstalled. Did I miss an important detail? Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
Helmut Schneider wrote: === perl-threaded-5.10.1 conflicts with installed package(s): perl-threaded-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Yes. This has been the subject of some debate on the questi...@... list recently. The behaviour you're seeing is the result of a recent commit affecting the conflicts handling code in bsd.port.mk. It now checks for conflicts much earlier -- during the fetch and build phases of installing from a port. Consequently the common idiom of: # portupgrade -o new-variant -f old-variant will almost always result in an error as you've seen. Many people (myself included) think this change is not a good idea. To work around the problem, try: # portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f perl-threaded-5.8.\* and then carry on the process as described in UPDATING by force-upgrading all perl modules and any applications that embed a perl interpreter (mod_perl, net-snmpd, nagios, etc) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: How to upgrade perl 5.8 to 5.10?
On Wed, Jan 20, 2010 at 1:54 PM, Helmut Schneider jumpe...@gmx.de wrote: [...] Currently the only solution seems to remove perl.5.8 which as a result deletes all dependencies which requires *all* ports to be reinstalled. No way, only if you decide to deinstall everything recursively. What about: # pkg_deinstall -vfu perl-threaded-5.8.9_3 # portinstall -v lang/perl5.10 # portupgrade -vfu p5\* (Also, cross-checking with /usr/local/bin/perl-after-upgrade helps with some other specific cases). m. ___ 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: How to upgrade perl 5.8 to 5.10?
Matthew Seaman wrote: Helmut Schneider wrote: === perl-threaded-5.10.1 conflicts with installed package(s): perl-threaded-5.8.9_3 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Yes. This has been the subject of some debate on the questi...@... list recently. The behaviour you're seeing is the result of a recent commit affecting the conflicts handling code in bsd.port.mk. It now checks for conflicts much earlier -- during the fetch and build phases of installing from a port. Consequently the common idiom of: # portupgrade -o new-variant -f old-variant will almost always result in an error as you've seen. Many people (myself included) think this change is not a good idea. To work around the problem, try: # portupgrade -m DISABLE_CONFLICTS=yes -o lang/perl5.10 -f perl-threaded-5.8.\* and then carry on the process as described in UPDATING by force-upgrading all perl modules and any applications that embed a perl interpreter (mod_perl, net-snmpd, nagios, etc) top-notch! Thanks, Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
Michal Varga wrote: On Wed, Jan 20, 2010 at 1:54 PM, Helmut Schneider jumpe...@gmx.de wrote: [...] Currently the only solution seems to remove perl.5.8 which as a result deletes all dependencies which requires all ports to be reinstalled. No way, only if you decide to deinstall everything recursively. What about: # pkg_deinstall -vfu perl-threaded-5.8.9_3 # portinstall -v lang/perl5.10 # portupgrade -vfu p5\* # pkg_info -R perl-threaded-5.8.9_3 | grep -v ^p5 Information for perl-threaded-5.8.9_3: Required by: amavisd-new-2.6.4_4,1 apache-2.2.14_5 bsdpan-SNMP-Extension-PassPersist-0.03 gamin-0.1.10_3 gio-fam-backend-2.22.4 glib-2.22.4 mailgraph-1.14_2 nagios-plugins-1.4.14,1 net-snmp-5.4.2.1_6 pango-1.26.2 razor-agents-2.84 rpm2cpio-1.2_2 rrdtool-1.3.9 # (Also, cross-checking with /usr/local/bin/perl-after-upgrade helps with some other specific cases). I did so when I upgraded from 5.8.8 to 5.8.9. I finally found myself doing a portupgrade -af. :) -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
On Wed, Jan 20, 2010 at 2:58 PM, Helmut Schneider jumpe...@gmx.de wrote: # pkg_info -R perl-threaded-5.8.9_3 | grep -v ^p5 Information for perl-threaded-5.8.9_3: Required by: amavisd-new-2.6.4_4,1 apache-2.2.14_5 bsdpan-SNMP-Extension-PassPersist-0.03 gamin-0.1.10_3 gio-fam-backend-2.22.4 glib-2.22.4 mailgraph-1.14_2 nagios-plugins-1.4.14,1 net-snmp-5.4.2.1_6 pango-1.26.2 razor-agents-2.84 rpm2cpio-1.2_2 rrdtool-1.3.9 # (Also, cross-checking with /usr/local/bin/perl-after-upgrade helps with some other specific cases). I did so when I upgraded from 5.8.8 to 5.8.9. I finally found myself doing a portupgrade -af. :) I'm not a heavy Perl user, but I don't remember anything ever melting too much, while doing it this way. Of course, there are things like irssi, that break -every time- you reinstall Perl (even the same version), but one gets used to it quickly. Then there is the rest that probably only execs some scripts with Perl and doesn't care about your versions (much). Majority of your, or mine, installed ports have Perl only as an inherited dependency and never directly use it, so -af is a bit overkill in such cases, i mean: pkg_info | wc -l 805 Whew. So even when you're switching near-major versions, recompiling p5-* and maybe some of those in your list (I'd randomly pick, say amavisd, bsdpan- and razor) should be enough, the fallout will be minimal, if any (and if so, you just rebuild that one more that still fails). Nevertheless, your list in't that extensive, recompiling all of it shouldn't take more than half an hour, that's still a bit cheaper than -af :) m. ___ 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: How to upgrade perl 5.8 to 5.10?
Michal Varga wrote: I'm not a heavy Perl user, but I don't remember anything ever melting too much, while doing it this way. Of course, there are things like irssi, that break -every time- you reinstall Perl (even the same version), but one gets used to it quickly. Then there is the rest that probably only execs some scripts with Perl and doesn't care about your versions (much). Majority of your, or mine, installed ports have Perl only as an inherited dependency and never directly use it, so -af is a bit overkill in such cases, i mean: pkg_info | wc -l 805 Hell! So even when you're switching near-major versions, recompiling p5-* and maybe some of those in your list (I'd randomly pick, say amavisd, bsdpan- and razor) should be enough, the fallout will be minimal, if any (and if so, you just rebuild that one more that still fails). Nevertheless, your list in't that extensive, recompiling all of it shouldn't take more than half an hour, that's still a bit cheaper than -af :) # pkg_info | wc -l 457 # And this machine is even my package-building station! Anyway, portupgrade -af took 45 minutes. *g* # dmesg -a [...] CPU: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz (2500.10-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDC M,DCA,SSE4.1 AMD Features=0x2800SYSCALL,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8256348160 (7873 MB) ACPI APIC Table: IBMSERBLADE FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn ___ 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: How to upgrade perl 5.8 to 5.10?
# pkg_info | wc -l 457 # And this machine is even my package-building station! Anyway, portupgrade -af took 45 minutes. *g* Well, it's a dedicated blade after all :) And those 8 cores seem pretty nasty, I'm envious. That 800+ installed ports are for a regular desktop system, CPU: AMD Phenom(tm) 8450 Triple-Core Processor (2109.74-MHz 686-class CPU) Cores per package: 3 just things like xul/firefox, or webkit alone take an hour to build. Think of 2 to 3 days to recompile everything from scratch. And that's only for a Gnome desktop setup, throw in another KDE environment to the mix and their family of applications and you can round that to a week (maybe slightly less if you leave the machine running completely dedicated). While your blade would cut that time down considerably, it still wouldn't be in minutes anymore :) m. ___ 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: How to upgrade perl 5.8 to 5.10?
Michal Varga wrote: # pkg_info | wc -l 457 # And this machine is even my package-building station! Anyway, portupgrade -af took 45 minutes. g Well, it's a dedicated blade after all :) And those 8 cores seem pretty nasty, I'm envious. Well, afaik I even cannot use more than one CPU when building ports. There were plans/rumors that this would change. Does anyone know more about it? ___ 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: How to upgrade perl 5.8 to 5.10?
Helmut Schneider wrote: Michal Varga wrote: # pkg_info | wc -l 457 # And this machine is even my package-building station! Anyway, portupgrade -af took 45 minutes. g Well, it's a dedicated blade after all :) And those 8 cores seem pretty nasty, I'm envious. Well, afaik I even cannot use more than one CPU when building ports. There were plans/rumors that this would change. Does anyone know more about it? ___ 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 It has happened: http://lists.freebsd.org/pipermail/freebsd-ports/2009-March/053736.html I believe *dependencies* of a port will be compiled using one process (and thus CPU) at a time, however. -Boris ___ 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: How to upgrade perl 5.8 to 5.10?
Well, it's a dedicated blade after all :) And those 8 cores seem pretty nasty, I'm envious. Well, afaik I even cannot use more than one CPU when building ports. There were plans/rumors that this would change. Does anyone know more about it? Sure you can, as Boris (below) linked, this happened long time ago, especially: You don't need to do anything to enable the new feature. Whitelisted ports will automatically make use of all processors available in your computer. Most large ports I have seen (and use) luckily take advantage of all available processors during build (which completely sucks for desktop systems, but then, you normally shouldn't do that on a station where you try to work, so I'm fine with that). There's no way you'd be able to build 450 ports in 45 minutes if you were using only one CPU/core. It has happened: http://lists.freebsd.org/pipermail/freebsd-ports/2009-March/053736.html I believe *dependencies* of a port will be compiled using one process (and thus CPU) at a time, however. Interesting, are you sure this really happens? At least I understand you mean that - let's say - when i choose to compile, i.e. www/webkit directly, it will use all available processors (which it does, all the time), but when I try to compile, say, www/epiphany, which pulls www/webkit as a dependency, it will get built without MAKE_JOBS_SAFE, locked to a single processor? I can test in a short while if that's really the way, just asking, if I got you right.. m. ___ 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
