From owner-freebsd-ports@FreeBSD.ORG Mon Jun 7 01:55:53 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 713DC16A4CE; Mon, 7 Jun 2004 01:55:53 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02C8543D1D; Sun, 6 Jun 2004 18:55:53 -0700 (PDT) (envelope-from Barbish3@adelphia.net) Received: from barbish ([67.20.101.71]) by mta9.adelphia.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with SMTP id <20040607015552.CQHS26615.mta9.adelphia.net@barbish>; Sun, 6 Jun 2004 21:55:52 -0400 From: "JJB" To: Date: Sun, 6 Jun 2004 21:55:51 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal cc: ports@FreeBSD.org Subject: FreeBSD Port: p5-Net-Netmask-1.9011 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barbish3@adelphia.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 01:55:53 -0000 Lars Thanks for the heads up that you fixed p5-Net-Netmask. But I have bad news. It did not fix the problem totally. It got rid of the error message about warning, but now I get msg "could not parse" pointing to this line in my perl script $t=new Net::Netmask($value); Let me state the circumstances again. I was running 4.9 stable with what ever perl version that comes with it, and had done pkg_add -r p5-Net-Netmask and my scripts that use netmask were working just fine. They are stable and have not been touched in any way. 6/2/04 I installed 4.10 stable from downloaded cdrom1.iso file and redid pkg_add -r p5-Net-Netmask, that is when I reported the original problem about the error message warning. After receiving your email that you had fixed the problem I checked and saw the package was not updated so today I installed the port version and now I am getting the "could not parse" message. As side info, today in the questions list there was an post from an new 4.10 user who lost all his -cpan modules during source upgrade and can not get "perl -MCPAN -e shell" to work. This is the same problem I reported to you I was having with cpan. I don't want to be the bearer of bad news, but early indications point to an problem with the configuration of perl in the new 4.10 stable release. Please take the necessary steps to notify the correct people who have authority to look into this problem and correct it. I just hope it does not take an 4.10.1 stable release to correct it, or an mandatory install of the perl port. Please keep me informed as to what is happening so I can test any fixes and report back. Thanks Joe