From owner-freebsd-arch Tue Dec 19 18: 3:28 2000 From owner-freebsd-arch@FreeBSD.ORG Tue Dec 19 18:03:26 2000 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 5E46337B400 for ; Tue, 19 Dec 2000 18:03:26 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id C20959CD; Tue, 19 Dec 2000 18:03:25 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id SAA04724; Tue, 19 Dec 2000 18:03:14 -0800 (PST) Sender: marcel@cup.hp.com Message-ID: <3A401362.6EA9E607@cup.hp.com> Date: Tue, 19 Dec 2000 18:03:14 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug Barton Cc: arch@FreeBSD.ORG Subject: Re: A perlified gensetdefs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > > > > > In order to reduce the number of ELF specific tools, I rewrote > > > > gensetdefs(1) in perl > > > > > > Not to rain on your parade, but personally I'd rather see the amount of > > > perl in the base reduced instead of increased. Is there a way to solve > > > the cross-build problems without making this into a perl script? > > > > What cross-build problems are you refering to? > > Your stated purpose for making this a perl script was to "reduce > the number of ELF specific tools," so I'm wondering why that's a priority, > and if it could possibly be solved with a different method. Porting FreeBSD to non-supported platforms can be made a bit more easy if we can reduce the overall number of home brewn tools and instead use tools provided by the GNU toolchain. Not only does it allow non-ELF ports, but also help to support big endian ports and other strangeness we don't think about right now. I choose perl(1) because I couldn't find a sufficiently efficient solution otherwise. I've given it some more thought and can probably do it with sed(1), awk(1) and the likes. The only objection I've had so far is that we should not depend on perl(1) and I can see why, so I'm going to rewrite the script... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message