Gregory Keeney wrote:
Thomas Seiler wrote:
Couldn't we split the probing into two phases ?
The problem is that getting stuff on and off your target host is not
always trivial. [...]
It is especially not true in the embedded world. Until I have parrot IO
libraries, I am not going to be getting a
Thomas Seiler wrote:
Couldn't we split the probing into two phases ?
Let's asume for a moment that it's easy to build a miniparrot for
ethier the host or the target.
The first phase would run on the host and prepare the tests and a
miniparrot for the target, but not run them.
The seconde phase
Gregory Keeney wrote:
Rhys Weatherley wrote:
What autoconf database? Autoconf uses probing for cross-compilation as
well.
Essentially, you use the cross-compiler's knowledge of the platform to
act as the "database". You just need to be clever in how you format
the query.
>
I don't think Parrot
At 3:32 PM -0700 9/8/04, Gregory Keeney wrote:
Rhys Weatherley wrote:
What autoconf database? Autoconf uses probing for cross-compilation as well.
i.e. it runs the cross-compiler and sees what succeeds and what
fails. Some things are tricky, like detecting type sizes and
endianness, because you
On Thursday 09 September 2004 08:32 am, Gregory Keeney wrote:
> I don't think Parrot's probe system can help us here. Autoconf (as
> described above) uses the target architecture compiler's knowledge of
> the target system. We don't have anything equivalent, as we want to
> bootstrap the cross com
