Date: Thu, 21 Dec 2000 10:35:49 +1100 From: Benno Rice <benno@FreeBSD.org> To: freebsd-arch@FreeBSD.ORG Subject: Re: gensetdefs using sh(1),sed(1),grep(1) and awk(1) Message-ID: <20001221103548.A10223@rafe.jeamland.net> In-Reply-To: <20001220115432.B10298@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Dec 20, 2000 at 11:54:32AM -0800 References: <3A405A43.5C10697C@cup.hp.com> <20001219233816.H19572@fw.wintelcom.net> <3A40F2EB.C43F0A88@cup.hp.com> <20001220103154.A9294@dragon.nuxi.com> <3A410ACB.3CB3C32@cup.hp.com> <20001220115432.B10298@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 20, 2000 at 11:54:32AM -0800, David O'Brien wrote: > On Wed, Dec 20, 2000 at 11:38:51AM -0800, Marcel Moolenaar wrote: > > The posted perl(1) and awk(1) versions should tell you what is required. > > These scripts are derived from our current C implementation in /usr/bin. > > Yes, and I still fail to see why one cannot build a gensetdefs binary > (ie, from C source) for the target machine manually and use that. From > the looks of it that is what DFR did for his IA-64 work. Because the current gensetdefs will refuse to deal with a target endianness that's different to the host's. This is why I put my support behind it in the first place. Note that personally I dislike perl, but I think that the perl version is far more readable than the sh one. If someone were to extend the C version to handle endian differences, I'd be more than happy to see that go in though. Basically, I don't care how it works, as long as it works and is maintainable. =) -- Benno Rice benno@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001221103548.A10223>