--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Joerg Sonnenberger <joerg@britannica.bec.de> wrote:
> On Thu, Aug 24, 2006 at 05:11:20PM -0400, Jan Schaumann wrote:
> > However, trying to build stuff on IRIX with gcc, I realize that an
> > additional CFLAGS (-std=3Dc99) is also required for gcc.  Instead of
> > patching the same number of packages again with an additional check, I
> > was thinking it might make more sense to simply add a=20
> >=20
> > USE_LANGUAGES+=3D	c99
>=20
> I prefer this. Does IRIX offer a c99 compiler frontend (as opposed to
> cc)? We could change CC=3Dc99 in this case.

IRIX MIPSPro does indeed provide a "c99" compiler frontend.  However,
this does not solve the problem when using gcc as the compiler.  Unless
we provide a wrapper for "c99" that invokes the appropriate compiler
with the right flags.

-Jan

--=20
   This is so cool I have to go to the bathroom.

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iD8DBQFE8jEkfFtkr68iakwRAljlAJ4rO0Hlr1B95PGI2WqKvN7oQvJm7ACg2FlG
RU/pSMgVv2ySDb8ESDiHsKg=
=TFkG
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--