Another Config task

[Dan Sugalski]

Something for people to work on, and something that can be worked on
piecemeal (which is good). We need to make parrot's build less
dependent on the flags set in the current perl install, especially
for things like the C compiler and linker flags.

So... if folks would like to take a shot, any and all bits and pieces
would be appreciated. Taking a look at perl's metaconfig stuff for
this (or, I suppose, autoconf's, though I expect that's a bit
gcc-specific) wouldn't be out of line either, and would save at least
a few of your brain cells as you looked at it. :)
--
Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk

[Leopold Toetsch]

Dan Sugalski <d...@sidhe.org> wrote:
> Something for people to work on, and something that can be worked on
> piecemeal (which is good). We need to make parrot's build less
> dependent on the flags set in the current perl install, especially
> for things like the C compiler and linker flags.

... and data types, I've to add. I've a home grown perl around from these
days, when it was needed, to build a parrot with "long double" support.
This perl is of course the default, because I've not found the time to
build another one[1] (and it doesn't hurt) except I now have to:

$ perl Configure.pl --floatval=double

to get again a default FLOATVAL size. The same story holds for INTVAL.

And due to all void* <=> INTVAL conversions, it's really unlikely that a
configuration that has different sizes for this type will ever work.

> So... if folks would like to take a shot,

... then thanks too,

leo

[1] which of course isn't true - I've another one with threads enabled -
but that doesn't really matter - a non-standard perl evokes too much
non-default config on parrot.