I was pretty averse to adding an additional configure step myself. The
problem is that warnings.pm checks specifically for supported compiler
flags and I didn't want to include other things there. The bug is that
gcc.pm is hardcoded for version 4.x rather than checking. I didn't want to
add
On 22/04/2008, Jeff Horwitz <[EMAIL PROTECTED]> wrote:
>
> On Tue, 22 Apr 2008, Donald Hunter wrote:
>
> hi donald!
>
> hm, i thought i committed the fix for this, but apparently not. check out
> r334 in the mod_parrot repository.
Great, that fixed my build problem,
her method?
Cheers,
Donald Hunter.
