I am an idiot...

[jsbowden]

Note to self:

When compiling software written to C99 standards, call the compiler so it actually knows it's SUPPOSED to be parsing ANSI code, not K&R.

That is all.

Comments

[paoconnell.livejournal.com]

I've programmed and compiled on an SGI O2, maybe 7 years ago, so my memory's fuzzy. We weren't trying to compile Gnu code, though.
I'd think that if you were trying to compile a lot of Gnu code you would want to set your compile defaults to something that compiles everything correctly, especially if you're doing custom programming on the workstation and want to use ANSI anyway.

[jsbowden.livejournal.com]

I'm not writing any code. I'm just trying to compile current versions of all the GNU software I have in /usr/local (which is an NFS share to all the SGIs on my network). Some of these utils I orginally compiled 6 years ago on Irix 6.2 on an Indy. The problem is that current SGI MIPSpro compilers behave differently depending how you call them, instead of the old way of setting CFLAGS="set your magic incantation for [ANSI|C90|C99] here". Last time I went through this, I could just set /etc/compiler.defaults to the way I wanted it and only override via environment variable if necessary for a specific piece of software. Last time I went through this, most of the GNU stuff that didn't require GCC was still primarily K&R or plain ANSI, which the compiler is generally smart enough to deal with on it's own. It's the newer ANSI [C90|C99] code that's making life interesting. That it can't seem to automagically handle.