RE: Problems running GCC on Solaris (include files)

["Rupert Wood" <me at rupey dot net>]

Max Heffler wrote:

> On another note, after configuring, I had to make a few changes to
> complete the build. There were complaints about "inline" so I
> changed the definitions to "#define inline /**/" since no other 
> options seemed to satisfy the compiler.

This sounds like you're building the guts of GCC with Sun cc. This
shouldn't happen; the system compiler should only be used to build GCC's
C compiler in stage1 of the bootstrap. The stage1 compiler should then
be used to build the rest and it accepts 'inline' in plain C.

May I check that you built GCC with 'make bootstrap' and not 'make'?

(As a side note, I don't think you needed the "/**/"; you can get away
with "#define inline". The last time I had to make this hack for Sun
Forte, though, I think I used "#define inline static": you won't be
relying on a function defined inline in a sourcefile to export, and if a
function defined inline in a header exports then you'll hit problems.)

I have no experience of Solaris 2.6 myself but it sounds like your other
problems should have been covered by GCC's 'fixincludes'. It might not
pick these up properly if you didn't bootstrap the compiler or didn't
"make install" it. If you don't want to install it, you'll need to add
an include path to the fixed headers in the gcc build tree (although I'm
afraid I forget exactly where).

Good luck,
Rup.