From owner-freebsd-ports Thu Apr 6 21:27:31 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA21799 for ports-outgoing; Thu, 6 Apr 1995 21:27:31 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA21793 for ; Thu, 6 Apr 1995 21:27:26 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id MAA17843; Fri, 7 Apr 1995 12:27:38 +0800 Date: Fri, 7 Apr 1995 12:27:37 +0800 (CST) From: Brian Tao To: FREEBSD-PORTS-L Subject: Re: perl 5.001 + gcc 2.6.3 + FreeBSD 2.0-950322-SNAP (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ports-owner@FreeBSD.org Precedence: bulk I bounced a bug report to Larry Wall and received an automated response (partially included below). I suppose the point is that any additional ones should go directly to perl5-porters@nicoh.com. Is anyone already on the list and can scan for fixes/patches that affect building perl5 on FreeBSD? I can watch the list until 5.002 comes out, but I think it would be better if someone who actually knew anything about perl could provide feedback to that list. :-/ -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org ---------- Forwarded message ---------- Date: Thu, 6 Apr 95 08:46:14 PDT From: Larry To: taob@gate.sinica.edu.tw Subject: Re: perl 5.001 + gcc 2.6.3 + FreeBSD 2.0-950322-SNAP [This is a recording. Last revision was the 5th of April.] Hi, I got your message, whatever it was. If you have a Perl question, and I don't answer right away, try comp.lang.perl. If you have a Perl 5 question, try mail to perl5-porters@nicoh.com. If you've sent me a Perl 5 bug report, I will probably forward it to that list. I wish I could send a personal reply to everyone but I'm usually pretty swamped. (The rest of the time, I'm totally swamped.) I do at least READ all my mail. Eventually. [...] If you're working with Perl 5 you might want to join the mailing list perl5-porters@nicoh.com to get the most recent patches and documentation. Known problems include: The kit is missing Andy's configuration notes. s/// leaks memory pad_findlex() is missing its prototype and can coredump (fix available) some systems wrongly attempt to re-byacc perly.y some compilers abhor the static declaration of emit_split in x2p/walk.c Tk needs some fixes to work with 5.001 "Unofficial" patches for some of these can be found at ftp://ftp.cis.ufl.edu/pub/perl/src/5.0/perl5.001.patches 5.001 might be considered a beta for 5.002. Expect 5.002 very soon.