From owner-freebsd-current Fri Nov 27 08:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04871 for freebsd-current-outgoing; Fri, 27 Nov 1998 08:25:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04866 for ; Fri, 27 Nov 1998 08:25:03 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id CAA24778 for ; Sat, 28 Nov 1998 02:54:55 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA26748; Sat, 28 Nov 1998 02:54:55 +1030 Date: Sat, 28 Nov 1998 02:54:55 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: Updated gperf? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been playing around with the egcs snapshots, and newer ones rely on a modified version of gperf 2.7 (gperf 2.1 is the version currently in 3.0). Can someone who actually understands what gperf does: 1) pronounce whether 2.7 is suitable for inclusion in the base tree (i.e. backwards-compatible for our needs, or whatever), and 2) take a look at ftp://egcs.cygnus.com/pub/egcs/infrastructure/gperf-2.7-19981006.pat and see whether this is a worthwhile patch to include? If not, what would be the best way to make the patched 2.7 available for use in building egcs (a gperf27 port?) I haven't checked with obrien, but from my own investigations this is probably one reason the ports snapshot hasn't been updated in the past month and a half. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message