> On Monday 19 March 2007 11:56, Andy Dougherty wrote:
>
> > The only way to tell for sure if you have a working compiler is to try to
> > compile and run something. After the user has been prompted for all the
> > flags, simply try to compile and run a simple test program. If it works,
> > fine
On Mon, Mar 19, 2007 at 02:56:03PM -0400, Andy Dougherty wrote:
> In my opinion, that way lies madness. Generating a list of options which
> all possible current and future compilers will accept is not only
> impossible, it's pointless. It's also aggravating that there's no way to
> override
On Monday 19 March 2007 08:19, Andy Dougherty wrote:
> This one falls over immediately during Configure. Even setting
> verbose=2, I don't see why:
>
> Parrot Version 0.4.9 Configure 2.0
> Copyright (C) 2001-2007, The Perl Foundation.
>
> [ . . . ]
>
> Determining what C compiler
On Monday 19 March 2007 11:56, Andy Dougherty wrote:
> On Mon, 19 Mar 2007, chromatic wrote:
> > The heuristic for detecting a compiler is to invoke it with some sort of
> > help flag, where $cc contains the executable name of your compiler:
> >
> > $cc -h
> > $cc --help
> > $cc /?
>
On Mon, 19 Mar 2007, chromatic wrote:
> On Monday 19 March 2007 08:19, Andy Dougherty wrote:
>
> > This one falls over immediately during Configure. Even setting
> > verbose=2, I don't see why:
> >
> > Parrot Version 0.4.9 Configure 2.0
> > Copyright (C) 2001-2007, The Perl Foundation.
>
On Wed, 14 Mar 2007, Will Coleda via RT wrote:
> Re: [perl #37178] [PATCH] Quiet a few alignment warnings
> Thanks, (belatedly) applied.
Wow. I'd completely given up hope on that one.
So feeling inspired, I decided to try it out and see how things looked.
Alas, my first attempt failed:
