From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ebee36cb10800b1e2f324a0b1b13e85f@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Wed, 14 Nov 2007 14:25:19 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Ruby port
In-Reply-To: <13426df10711141119s5433b14cx90615fd0c95404c4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: fa7bdd94-ead2-11e9-9d60-3106f5b1d025

> Put it another way. There are THOUSANDS of tools that you can't even
> attempt to compile if you can't run configure. You can't run configure
> w/out bash. You can't build bash unless you have the gnu toolchain.
> 
> It's a knot.
> 
> And the only way out that I can see is gcc.
> 
> ron

a good number of tools are not that hard to de-configure.  i've
had to stoop to that when compiling stuff for which configure is broken.

a good percentage of the stuff configured is not required.  configure
spends a lot of energy looking for spiffy optimizations that can safely
be skipped.

- erik