Subject: RE: /sparc-sun-solaris2.5 vs. sparc-sun-solaris2.6 (#sh -x build CC=gcc sol)

From: Magdalena Hewryk <[email-masked]>
Date: Mon, 17 May 1999 15:20:38 -0400

Gregory:

I found a workaround by using /opt/SUNWspro/bin/cc compiler instead of gcc.
It compiled with no errors.  
Probably the next step will be the upgrade of gcc. 

Thanks again for help.

Regards,
...Magda

-----Original Message-----
From: Gregory A Lundberg [mailto:[email-masked]]
Sent: Monday, May 17, 1999 1:01 PM
To: Magdalena Hewryk
Cc: [email-masked]'
Subject: RE: /sparc-sun-solaris2.5 vs. sparc-sun-solaris2.6 (#sh -x
build CC=gcc sol)

On Mon, 17 May 1999, Magdalena Hewryk wrote:

> Are you talking about Solaris upgrade?

I don't use Solaris.  What I was notiing was that the redefinition was
between two system headers.

On my systems, that usually happens when upgrading where the new version
moves the definition of something from one header to another and the old
header wasn't upgraded.  As long as the definitions are the same (they
usually are) I don't worry about it.

For instance, my Linux 4.2 production box has a similar warning when
compiling the daemon:

/usr/include/netdb.h:70: warning: `_PATH_HEQUIV' redefined
/usr/include/paths.h:55: warning: this is the location of the previous
definition

I've checked that the definitions are the same (they are) so I don't worry
about this warning.  I suppose I could edit one or the other header to
eliminate the warning, but I don't see any point to it ('sides, it might
break something else).

-- 

Gregory A Lundberg              Senior Partner, VRnet Company
1441 Elmdale Drive              [email-masked]
Kettering, OH 45409-1615 USA    1-800-809-2195