Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Step 1: We probe, and build a config file (not config.h, mind) with
> our results.
>
> Step 2: We take the config file and build config.h and choose (or
> build) the right platform.h/platform.c file.
Internally, Configure is a four-step process (initializ
At 12:03 PM -0700 9/8/04, Gregory Keeney wrote:
Dan Sugalski wrote:
The only problem I can forsee when doing cross-compilation is in
the building of the library files. Parrot itself... no big. We
build miniparrot for the platform you're on, then use the config
file to rebuild for the target plat
Dan Sugalski wrote:
The only problem I can forsee when doing cross-compilation is in the
building of the library files. Parrot itself... no big. We build
miniparrot for the platform you're on, then use the config file to
rebuild for the target platform. That part works out OK, but the
resulting
Okay, now that we've gotten past the autoconf thing, time to tackle
the cross-compilation thing, as well as the "what exactly did I
choose last time when I built this stuff" thing.
It seems to me that the sensible thing to do is take the environment
probing in two steps.
Step 1: We probe, and
