rrdtool and perl 5.10 not playing nice
I have seen this issue on two machines now, but this particular instance is on a newly built one. I run munin to collect and graph stats on my network from this box. net-mgmt/munin-master depends on perl and rrdtool. I installed perl 5.10 from ports and then installed munin-master. rrdtool was built as a dependency with the default port knobs: r...@aylee /usr/ports/databases/rrdtool # make showconfig === The following configuration options are available for rrdtool-1.4.3: DEJAVU=off Use DejaVu fonts (requires X11) MMAP=on Use mmap in rrd_update PERL_MODULE=on Build PERL module PYTHON_MODULE=off Build PYTHON bindings RUBY_MODULE=off Build RUBY bindings I'm seeing this error from munin: Can't locate RRDs.pm in @INC (@INC contains: /usr/local/lib/perl5/5.10.1/BSDPAN /usr/local/lib/perl5/site_perl/5.10.1/mach +/usr/local/lib/perl5/site_perl/5.10.1 /usr/local/lib/perl5/5.10.1/mach /usr/local/lib/perl5/5.10.1 .) at +/usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Utils.pm line 22. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Utils.pm line 22. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/UpdateWorker.pm line 18. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/UpdateWorker.pm line 18. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Update.pm line 17. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Update.pm line 17. Compilation failed in require at /usr/local/share/munin/munin-update line 13. BEGIN failed--compilation aborted at /usr/local/share/munin/munin-update line 13. RRDs.pm does exist: r...@aylee /root # find /usr/local/lib/perl5 -name RRDs.pm /usr/local/lib/perl5/site_perl/5.10.1/Log/Log4perl/Appender/RRDs.pm Not knowing anything of perl, what can I do to fix this? It has only occurred since upgrading to/installing perl 5.10 cheers, Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rrdtool and perl 5.10 not playing nice
On 13 July 2010 22:59, Rob Byrnes rbyr...@gmail.com wrote: I have seen this issue on two machines now, but this particular instance is on a newly built one. I run munin to collect and graph stats on my network from this box. net-mgmt/munin-master depends on perl and rrdtool. I installed perl 5.10 from ports and then installed munin-master. rrdtool was built as a dependency with the default port knobs: r...@aylee /usr/ports/databases/rrdtool # make showconfig === The following configuration options are available for rrdtool-1.4.3: DEJAVU=off Use DejaVu fonts (requires X11) MMAP=on Use mmap in rrd_update PERL_MODULE=on Build PERL module PYTHON_MODULE=off Build PYTHON bindings RUBY_MODULE=off Build RUBY bindings I'm seeing this error from munin: Can't locate RRDs.pm in @INC (@INC contains: /usr/local/lib/perl5/5.10.1/BSDPAN /usr/local/lib/perl5/site_perl/5.10.1/mach +/usr/local/lib/perl5/site_perl/5.10.1 /usr/local/lib/perl5/5.10.1/mach /usr/local/lib/perl5/5.10.1 .) at +/usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Utils.pm line 22. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Utils.pm line 22. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/UpdateWorker.pm line 18. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/UpdateWorker.pm line 18. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Update.pm line 17. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.10.1/Munin/Master/Update.pm line 17. Compilation failed in require at /usr/local/share/munin/munin-update line 13. BEGIN failed--compilation aborted at /usr/local/share/munin/munin-update line 13. RRDs.pm does exist: r...@aylee /root # find /usr/local/lib/perl5 -name RRDs.pm /usr/local/lib/perl5/site_perl/5.10.1/Log/Log4perl/Appender/RRDs.pm Not knowing anything of perl, what can I do to fix this? It has only occurred since upgrading to/installing perl 5.10 More info - while using portmaster -f rrdtool to forcibly reinstall rrdtool, I get these messages: pkg_delete: package 'rrdtool-1.4.3' is required by these other packages and may not be deinstalled (but I'll delete it anyway): munin-master-1.4.4 pkg_delete: file '/usr/local/lib/perl5/5.10.1/man/man3/RRDs.3.gz' doesn't exist pkg_delete: file '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/RRDs/RRDs.so' doesn't exist pkg_delete: file '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/RRDs/RRDs.bs' doesn't exist pkg_delete: file '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/RRDs/.packlist' doesn't exist pkg_delete: file '/usr/local/lib/perl5/site_perl/5.10.1/mach/RRDs.pm' doesn't exist pkg_delete: file '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/RRDs' doesn't exist pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/site_perl/5.10.1/mach/auto/RRDs' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) so it appears that these files are not actually being installed - could this be a bug in rrdtool or the port? cheers, Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: amavisd - exited on signal 11 - FreeBSD 8 with Perl 5.10
* Hans F. Nordhaug hans.f.nordh...@himolde.no [2010-04-29]: * Hans F. Nordhaug hans.f.nordh...@himolde.no [2010-04-29]: Hi! I have been happily running Postfix with amavisd-new (and Clamav and SpamAssassin) on FreeBSD 7 with Perl 5.8 for a long time. Recently, I upgraded to FreeBSD 8 and rebuilt all ports (after updating). Suddenly I saw many kernel: pid x (perl), uid 110: exited on signal 11 lines in /var/log/messages and mailq returns some messages with comments like: (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once) Cutting a lot of debug statements here - see http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/215759.html for my complete original messages I finally found the problem - the spamassassin bayes db. For some reason Perl (or really spamassassin) exited on signal 11 when reading the bayes db. The reason it took my so long to find the problem was: 1) I was lazy and in stead of testing with su vscan -c 'spamassassin -D -t msg.txt' as recommended, I just ran spamassassin -D -t msg.txt as root. The later command didn't exit with signal 11, while the first did - it stopped after [...] check: pms new, time limit in 293.202 s locker: mode is 384 locker: safe_lock: created /var/amavis/.spamassassin/bayes.mutex locker: safe_lock: trying to get lock on /var/amavis/.spamassassin/bayes with 10 timeout locker: safe_lock: link to /var/amavis/.spamassassin/bayes.mutex: link ok bayes: tie-ing to DB file R/W /var/amavis/.spamassassin/bayes_toks bayes: tie-ing to DB file R/W /var/amavis/.spamassassin/bayes_seen bayes: found bayes db version 3 2) The debug in /var/log/maillog (as posted in my earlier messages) was [...] bayes: tie-ing to DB file R/W /var/amavis/.spamassassin/bayes_toks bayes: tie-ing to DB file R/W /var/amavis/.spamassassin/bayes_seen bayes: found bayes db version 3 locker: refresh_lock: refresh /var/amavis/.spamassassin/bayes.lock It didn't stop at the same point - bayes: found bayes db version 3. 3) sa-learn didn't report any problems with the bayes db. Anyway, the solution was simple - rm -rf /var/amavis/.spamassassin/*. I guess I should have asked on the amavisd mailing list, but at least this is documented here now for other FreeBSD users that get this problem after upgrading from Perl 5.8 to 5.10. Regards, Hans Nordhaug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
amavisd - exited on signal 11 - FreeBSD 8 with Perl 5.10
Hi! I have been happily running Postfix with amavisd-new (and Clamav and SpamAssassin) on FreeBSD 7 with Perl 5.8 for a long time. Recently, I upgraded to FreeBSD 8 and rebuilt all ports (after updating). Suddenly I saw many kernel: pid x (perl), uid 110: exited on signal 11 lines in /var/log/messages and mailq returns some messages with comments like: (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once) I Googled and found that this could be related to do_ascii/UUlib and disabled do_ascii in /usr/local/etc/amavisd.conf. That didn't fix it. Then I read somewhere that this could be caused by problems with nested regexp and that Perl 5.10 didn't have that problem. I upgraded to Perl 5.10.1 (and rebuild all ports depending on it) and that also didn't fix it. Currently all my port are up-to-date. I'm trying to log everything - $sa_debug = 'all'; and $log_level = 5; in amavisd.conf, but I don't really see the problem. Recent example: /var/log/messages == Apr 29 22:49:21 nordhaug kernel: pid 74726 (perl), uid 110: exited on signal 11 /var/log/debug.log == Apr 29 22:49:20 nordhaug amavis[74726]: Net::Server: 2010/04/29-22:49:20 CONNECT TCP Peer: 127.0.0.1:32829 Local: 127.0.0.1:10024 Apr 29 22:49:20 nordhaug amavis[74726]: loaded base policy bank [ ... skipped many debug lines from amavis[74726] ... ] Apr 29 22:49:20 nordhaug amavis[74726]: (74726-01) SpamControl: calling spam scanner SpamAssassin Apr 29 22:49:20 nordhaug amavis[74726]: (74726-01) timer set to 320 s for SA (was 480 s) Apr 29 22:49:20 nordhaug amavis[74726]: (74726-01) calling SA parse, SA version 3.3.1, 3.003001, data as GLOB Apr 29 22:49:20 nordhaug amavis[74726]: (74726-01) CALLING SA check Apr 29 22:49:21 nordhaug amavis[10435]: Net::Server: Starting 1 children Apr 29 22:49:21 nordhaug amavis[75502]: Net::Server: Child Preforked (75502) Apr 29 22:49:21 nordhaug amavis[75502]: entered child_init_hook Apr 29 22:49:21 nordhaug amavis[75502]: SpamControl: init_child on SpamAssassin done So, is anyone else seeing this? Can you give me any hints? I'm happy to give you more input if it is possible to turn on more debugging. Best regards, Hans PS! The message is sent eventually - the mail queue doesn't grow. And the server has a very light load. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: amavisd - exited on signal 11 - FreeBSD 8 with Perl 5.10
* Hans F. Nordhaug hans.f.nordh...@himolde.no [2010-04-29]: Hi! I have been happily running Postfix with amavisd-new (and Clamav and SpamAssassin) on FreeBSD 7 with Perl 5.8 for a long time. Recently, I upgraded to FreeBSD 8 and rebuilt all ports (after updating). Suddenly I saw many kernel: pid x (perl), uid 110: exited on signal 11 lines in /var/log/messages and mailq returns some messages with comments like: (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once) I Googled and found that this could be related to do_ascii/UUlib and disabled do_ascii in /usr/local/etc/amavisd.conf. That didn't fix it. Then I read somewhere that this could be caused by problems with nested regexp and that Perl 5.10 didn't have that problem. I upgraded to Perl 5.10.1 (and rebuild all ports depending on it) and that also didn't fix it. Currently all my port are up-to-date. I'm trying to log everything - $sa_debug = 'all'; and $log_level = 5; in amavisd.conf, but I don't really see the problem. Recent example: /var/log/messages == Apr 29 22:49:21 myserver kernel: pid 74726 (perl), uid 110: exited on signal 11 /var/log/debug.log == Apr 29 22:49:20 myserver amavis[74726]: Net::Server: 2010/04/29-22:49:20 CONNECT TCP Peer: 127.0.0.1:32829 Local: 127.0.0.1:10024 Apr 29 22:49:20 myserver amavis[74726]: loaded base policy bank [ ... skipped many debug lines from amavis[74726] ... ] Apr 29 22:49:20 myserver amavis[74726]: (74726-01) SpamControl: calling spam scanner SpamAssassin Apr 29 22:49:20 myserver amavis[74726]: (74726-01) timer set to 320 s for SA (was 480 s) Apr 29 22:49:20 myserver amavis[74726]: (74726-01) calling SA parse, SA version 3.3.1, 3.003001, data as GLOB Apr 29 22:49:20 myserver amavis[74726]: (74726-01) CALLING SA check Apr 29 22:49:21 myserver amavis[10435]: Net::Server: Starting 1 children Apr 29 22:49:21 myserver amavis[75502]: Net::Server: Child Preforked (75502) Apr 29 22:49:21 myserver amavis[75502]: entered child_init_hook Apr 29 22:49:21 myserver amavis[75502]: SpamControl: init_child on SpamAssassin done So, is anyone else seeing this? Can you give me any hints? I'm happy to give you more input if it is possible to turn on more debugging. OK, SA seems to log to /var/log/maillog so here we go: [ ... skipped many SA dbg lines ...] Apr 29 22:49:20 myserver amavis[74726]: (74726-01) SA dbg: locker: safe_lock: created /var/amavis/.spamassassin/bayes.lock.nordhaug.priv.no.74726 Apr 29 22:49:20 myserver amavis[74726]: (74726-01) SA dbg: locker: safe_lock: trying to get lock on /var/amavis/.spamassassin/bayes with 0 retries Apr 29 22:49:20 myserver amavis[74726]: (74726-01) SA dbg: locker: safe_lock: breaking stale /var/amavis/.spamassassin/bayes.lock: age=1272573511 now=1272574160 Apr 29 22:49:21 myserver amavis[74726]: (74726-01) SA dbg: locker: safe_lock: trying to get lock on /var/amavis/.spamassassin/bayes with 1 retries Apr 29 22:49:21 myserver amavis[74726]: (74726-01) SA dbg: locker: safe_lock: link to /var/amavis/.spamassassin/bayes.lock: link ok Apr 29 22:49:21 myserver amavis[74726]: (74726-01) SA dbg: bayes: tie-ing to DB file R/W /var/amavis/.spamassassin/bayes_toks Apr 29 22:49:21 myserver amavis[74726]: (74726-01) SA dbg: bayes: tie-ing to DB file R/W /var/amavis/.spamassassin/bayes_seen Apr 29 22:49:21 myserver amavis[74726]: (74726-01) SA dbg: bayes: found bayes db version 3 Apr 29 22:49:21 myserver amavis[74726]: (74726-01) SA dbg: locker: refresh_lock: refresh /var/amavis/.spamassassin/bayes.lock Apr 29 22:49:21 myserver postfix/lmtp[75499]: 595818A07C: to=x...@myserver, relay=127.0.0.1[127.0.0.1]:10024, delay=1.1, delays=0.06/0.01/0.01/0.98, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once) Apr 29 22:49:21 myserver amavis[75502]: TIMING [total 4 ms] - bdb-open: 4 (100%)100, rundown: 0 (0%)100 This didn't make it clearer for me, but maybe for you? Best regards, Hans ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Port of perl 5.10
Hi is there anyone working on a port of perl5.10? I can only see ports of 5.8 and 5.6. I can make a port of 5.10, it seems to compile flawlessly on FreeBSD 7. Have a good day Valerio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Port of perl 5.10
Valerio Daelli writes: is there anyone working on a port of perl5.10? I can only see ports of 5.8 and 5.6. I can make a port of 5.10, it seems to compile flawlessly on FreeBSD 7. _Many_ ports depend on perl, and each must be tested (and if broken hopefully fixed) before such an ungrade happens. I believe the recent jump from 5.8.8 to 5.8.9 took weeks of behind-the-scenes work. Now imagine what moving to 5.10 will likely involve Experienced help is always appreciated, and I commend the 20090113 entry of ports/UPDATING as having a contact point. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
On Tuesday 23 December 2008 03:27:19 Jerry wrote: Since it does seem to work quite well under Linux, I was wondering if there was some fundamental flaw in FBSD that prevented it from working correctly here. Even so, failing to get a major project like Perl running properly in over a year on FBSD does not bode well for the OS. Aside from the rest said in this thread, maybe you should consider the fact that it's a cross platform scripting language's responsibility to provide compatibility for the operating system, not the other way around. Also, Perl should really be cremated already, but you can file that under 'opinion'. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
Bruce Cran wrote: On Thu, 25 Dec 2008 18:47:21 -0700 Tim Judd taj...@gmail.com wrote: Jerry wrote: On Tue, 23 Dec 2008 04:06:46 -0800 (PST) Dr. Jennifer Nussbaum bg271...@yahoo.com wrote: Its now just over a year since Perl 5.10.0 was relased, but its still not in FreeBSD. (/usr/ports/lang only has 5.8). [...] on the contrary, when 5.8 was released, it took a long time to move to that. And when I asked that question on IRC (why 5.10 isn't currently used), it was described to me that the 5.6 to 5.8 move broke everything and caused lots of headache. World and Kernel used to (at least) use perl as a glue to make stuff works. I bet there's at least some 5.8 glue for world or kernel. perl was removed from the base system back in 2002 (http://lists.freebsd.org/pipermail/freebsd-announce/2002-May/000823.html) so there can't be anything in the world or kernel build that depends on it. It's one of the first things installed during an initial ports installation though. It is still true that the change from 5.6 to 5.8 was very disruptive because it broke lots of things in the ports tree. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
On Fri, 26 Dec 2008 12:45:12 + Kris Kennaway k...@freebsd.org wrote: [snip] It is still true that the change from 5.6 to 5.8 was very disruptive because it broke lots of things in the ports tree. Is this the official reason that Perl-5.10 has not been released into the ports tree? Are ports being tied to specific versions of Perl? I did some Googling and found that of the users that have installed Perl from source on FBSD, most were not experiencing any major problem. If every time Perl is updated it will require massive changes or whatever to the FBSD ports, then perhaps there is a fundamental flaw in the ports system to start with. Perhaps you could list what the specific problems are so that others might start looking for solutions. This is really the first time that I have become aware of problems between Perl and the ports system. Just my 2¢. -- Jerry ges...@yahoo.com I poured spot remover on my dog. Now he's gone. Steven Wright signature.asc Description: PGP signature
Re: Perl 5.10?
Jerry ges...@yahoo.com writes: Are ports being tied to specific versions of Perl? I did some Googling and found that of the users that have installed Perl from source on FBSD, most were not experiencing any major problem. If every time Perl is updated it will require massive changes or whatever to the FBSD ports, then perhaps there is a fundamental flaw in the ports system to start with. There is no requirement any port use Perl. Many do. There is no requiremment that any Perl-using port use a particular version. Many - I would guess most - do, at least to the extent of requiring the same major version (e.g. 5.x). There are 63 instances of USE_PERL5 in ports/textproc alone. I'm not a major direct Perl user, but I remember the jumps from 5.0 to 5.6 and from 5.6 to 5.8. Both required the testing of every affected port, and as I remember it problems were discovered in both the ports and in the new Perl itself. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
Jerry wrote: On Fri, 26 Dec 2008 12:45:12 + Kris Kennaway k...@freebsd.org wrote: [snip] It is still true that the change from 5.6 to 5.8 was very disruptive because it broke lots of things in the ports tree. Is this the official reason that Perl-5.10 has not been released into the ports tree? Are ports being tied to specific versions of Perl? I did some Googling and found that of the users that have installed Perl from source on FBSD, most were not experiencing any major problem. If every time Perl is updated it will require massive changes or whatever to the FBSD ports, then perhaps there is a fundamental flaw in the ports system to start with. The issue with 5.8 was that the perl developers made various incompatible changes that broke lots of third party software included in the ports tree, which all had to be fixed. I don't know what the issue is with 5.10. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
Jerry wrote: On Tue, 23 Dec 2008 04:06:46 -0800 (PST) Dr. Jennifer Nussbaum bg271...@yahoo.com wrote: Its now just over a year since Perl 5.10.0 was relased, but its still not in FreeBSD. (/usr/ports/lang only has 5.8). Can someone tell me why? Is there any way to get it working stably? Is there any schedule for when it will be added? This is a major release of a major language, not an obscure maintenence update. I asked that same question on the FreeBSD-Ports forum a few months ago; however, I never did receive a satisfactory answer. I believe it is readily apparent that it will not be included with the next release of FreeBSD; i.e., '7.1'. Since it does seem to work quite well under Linux, I was wondering if there was some fundamental flaw in FBSD that prevented it from working correctly here. Even so, failing to get a major project like Perl running properly in over a year on FBSD does not bode well for the OS. on the contrary, when 5.8 was released, it took a long time to move to that. And when I asked that question on IRC (why 5.10 isn't currently used), it was described to me that the 5.6 to 5.8 move broke everything and caused lots of headache. World and Kernel used to (at least) use perl as a glue to make stuff works. I bet there's at least some 5.8 glue for world or kernel. You can always download the source and compile it yourself. Perl's popular enough that I bet it'll compile fine. I hear it completely as: 1) World glue may break, and until you can be sure it'll work okay, wait. 2) Kernel glue may break, and until you can be sure it'll work okay, wait. 3) Ports glue/dependencies may break, and until you can be sure it'll work okay, wait. Given it's taken a year (I didn't realize it was that long) for this wait/check to happen, there must be something holding it up. You might be able to coexist 5.10 and 5.8 -- except the symlink 'perl' will point to ONE of them. I suggest you point it at 5.8 Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
On Thu, 25 Dec 2008 18:47:21 -0700 Tim Judd taj...@gmail.com wrote: Jerry wrote: On Tue, 23 Dec 2008 04:06:46 -0800 (PST) Dr. Jennifer Nussbaum bg271...@yahoo.com wrote: Its now just over a year since Perl 5.10.0 was relased, but its still not in FreeBSD. (/usr/ports/lang only has 5.8). [...] on the contrary, when 5.8 was released, it took a long time to move to that. And when I asked that question on IRC (why 5.10 isn't currently used), it was described to me that the 5.6 to 5.8 move broke everything and caused lots of headache. World and Kernel used to (at least) use perl as a glue to make stuff works. I bet there's at least some 5.8 glue for world or kernel. perl was removed from the base system back in 2002 (http://lists.freebsd.org/pipermail/freebsd-announce/2002-May/000823.html) so there can't be anything in the world or kernel build that depends on it. It's one of the first things installed during an initial ports installation though. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Perl 5.10?
Its now just over a year since Perl 5.10.0 was relased, but its still not in FreeBSD. (/usr/ports/lang only has 5.8). Can someone tell me why? Is there any way to get it working stably? Is there any schedule for when it will be added? This is a major release of a major language, not an obscure maintenence update. Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Perl 5.10?
On Tue, 23 Dec 2008 04:06:46 -0800 (PST) Dr. Jennifer Nussbaum bg271...@yahoo.com wrote: Its now just over a year since Perl 5.10.0 was relased, but its still not in FreeBSD. (/usr/ports/lang only has 5.8). Can someone tell me why? Is there any way to get it working stably? Is there any schedule for when it will be added? This is a major release of a major language, not an obscure maintenence update. I asked that same question on the FreeBSD-Ports forum a few months ago; however, I never did receive a satisfactory answer. I believe it is readily apparent that it will not be included with the next release of FreeBSD; i.e., '7.1'. Since it does seem to work quite well under Linux, I was wondering if there was some fundamental flaw in FBSD that prevented it from working correctly here. Even so, failing to get a major project like Perl running properly in over a year on FBSD does not bode well for the OS. -- Jerry ges...@yahoo.com When everything is coming your way, you are probably in the wrong lane. signature.asc Description: PGP signature
perl 5.10 port
Hello. I'm interesting when perl 5.10 will be available in freebsd ports? Always Want to ask same question about qt4.4. -- Regards, Nickolay D. Hodyunya. mailto: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
