2: compiling INN1.5.1sec2 -

2007-12-25 11:03:00

People pointed out that the reason my version of 'gcc' no longer works after the

operating system upgrade from Solaris 2.4 to Solaris 2.5 is that you either need

to re-install gcc or more quickly, run the "fixincludes" script included as part

of the gcc distribution.

This answer from Rich Pieri sums it up well:

"I can confirm that for you. GCC must be rebuilt when the OS is upgraded.

GCC relies upon information in the C include files, and because most

vendors ship "bad" inclueds it runs "fixincludes" to bring them up to ANSI

standards. When the OS is upgraded those headers change, but GCC's own

versions need to be updated. Simply running fixincludes again should be

sufficient, but a fresh rebuild will guarantee linking to the new

libraries."

Thanks to:

Nikos George

Ric Anderson

Rich Pieri

Erin O'Neill

Richard Hellier

Mark Heath

Jim Davis

Marina

______________________________ Forward Header __________________________________

Subject: SUMMARY: compiling INN1.5.1sec2 -

Author: Marina.Daniels@ccd.tas.gov.au (Marina Daniels) at Internet

Date: 8/8/97 4:45 PM

I made it compile using the 'sun c' compiler rather than gcc. I have a feeling

gcc is no longer properly installed on my machine since the operating system

upgrade.

Marina

______________________________ Forward Header __________________________________

Subject: compiling INN1.5.1sec2 - AARRGGGHHH

Author: Marina Daniels at CCD

Date: 8/8/97 3:34 PM

I would appreciate any help on this (such as PATH or LD_LIBRARY_PATH settings or

whatever worked for you) as I am getting desparate after 2 days of trying to

make this stupid program compile, and am in danger of smashing this machine to

bits.

I am trying unsuccesfully to compile INN1.5.1sec2 for Solaris 2.5 (SUN5), using

GCC and I've set the new variables to indicate I want to build my own

snprintf. (I've read all the FAQ's repeatedly so please don't tell me to do

that)

***Is this happening to anybody else?

in snprintf directory, the vnprintf.c

function has a line which says include xstdio.h in that directory but

this seems to redefine variables in stdio.h from the gcc include

directory?

Why is this a problem? Normally warning messages aren't fatal when

compiling.

Should I have my LD_LIBRARY_PATH variable set to get around this, or

similar?

cd frontends ; make all ; cd ..

gcc -I../include -DSUNOS5 -O2 -c inews.c

(cd ../snprintf ; make install)