Date: Wed, 29 Aug 2012 11:04:26 -0700 From: David Newman <dnewman@networktest.com> To: freebsd-questions@freebsd.org Subject: Re: Upgrading perl Message-ID: <503E59AA.7060605@networktest.com> In-Reply-To: <503E5872.9050805@networktest.com> References: <503BF131.4030803@sage-american.com> <44ehmp3k1a.fsf@be-well.ilk.org> <503E3071.7000905@sage-american.com> <503E5872.9050805@networktest.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/29/12 10:59 AM, David Newman wrote: > On 8/29/12 8:08 AM, Jack Stone wrote: >> On 8/29/2012 8:27 AM, Lowell Gilbert wrote: >>> Jack Stone <jacks@sage-american.com> writes: >>> >>>> uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD >>>> 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009 >>>> >>>> Running perl5.10 (yeah, old!) >>>> This is a production server. >>>> >>>> >>>> Been playing catchup on ports including perl as UPDATING recommends: >>>> portupgrade -o lang/perl5.12 -f perl-5.10.\* >>>> >>>> That has worked on other servers, but not this one. Anyone know what I >>>> need to do to clean this up?? >>>> >>>> But, can't get past this fatal error: >>>> mail# portupgrade -o lang/perl5.12 -f perl-5.10.\* >>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive >>>> specification: "WITHOUT_" >>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive >>>> specification: "WITHOUT_" >>>> make: fatal errors encountered -- cannot continue >>>> ** Makefile possibly broken: lang/perl5.12: >>> You're almost four years past the end-of-life on the release you're >>> running, so it's been left behind in terms of support. In this case it >>> looks (based on a *very* quick look) that you may be running into >>> changes in how make(1) actually works, in which case backporting the >>> ports functionality will be more work than it's worth. >>> >>> If the machine "can't" be updated, and assuming it's secure (which hard >>> to be sure about with old software on the Internet), you may be best off >>> leaving it alone. >>> >>> Good luck. >>> >>> >> Thanks for the reply. >> >> Actually, on other servers with the same upgrading needs, perl-5.12 >> installed without any issue. My intention is to upgrade perl in >> increments to get well past EOL. >> >> Wonder if I just deinstalled the old perl5-5.10 and then installed the >> perl5-12 would work. I can do that right from the port: make perl5-12 >> first to see if that works, then: >> # make deinstall (perl-5.10) then: make install clean > > If you're using portmaster, you should be able to do something like the > following from /usr/ports: > > portmaster -o lang/perl5.16 lang/perl5.10 > portmaster p5- > > and perl automagically will upgrade. Sorry, I'd missed that you'd tried this and it isn't working. make has changed since the 7.0 days. I agree with Jack that you're better off leaving well enough alone. If you really need perl5.16+ capabilities you're much better off moving your program to a more recent version of FreeBSD. dn > > This is from /usr/ports/UPDATING. You can also find instructions for > portupgrade there. > > Don't know about dependencies with 7.0, though. > > dn > > >> >> What do you think? I've got to move up because an important perl program >> requires a minimum 5.12. > > > >> > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?503E59AA.7060605>