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 12:26:34 -0400

Gregory,

re:  [...]the warnings about NBBY can be ignored.  They indicate the machine
was
upgraded from earlier versions and the job wasn't very well done [...]
--Question:
Are you talking about Solaris upgrade?

Would you give me an brief comment on /gcc-lib/sparc-sun-solaris2.5  
                                      /gcc-lib/ sparc-sun-solaris2.6 

--Question:
Do I have a problem with FTP compilation on Solaris 2.6 box because it has
/usr/home/usr_local/lib/gcc-lib/sparc-sun-solaris2.5   instead of 
/usr/home/usr_local/lib/gcc-lib/sparc-sun-solaris2.6   ?

Thanks,
...Magda

Output:
#sh -x build CC=gcc sol:

+ echo Making support library. 
Making support library.
+ cd ../support 
+ make CC=gcc libsupport.a 
gcc -O -DSOLARIS2  -c authuser.c
In file included from /usr/include/sys/turnstile.h:12,
                 from /usr/include/sys/t_lock.h:20,
                 from /usr/include/sys/vnode.h:37,
                 from /usr/include/sys/stream.h:21,
                 from /usr/include/netinet/in.h:38,
                 from /usr/include/netdb.h:96,
                 from authuser.c:20:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2.1/include/sys/param.h:187:
warning: `NBBY' redefined
/usr/include/sys/select.h:45: warning: this is the location of the previous
definition
In file included from /usr/include/sys/stream.h:26,
                 from /usr/include/netinet/in.h:38,
                 from /usr/include/netdb.h:96,
                 from authuser.c:20:
/usr/include/sys/model.h:32: #error "No DATAMODEL_NATIVE specified"
make: *** [authuser.o] Error 1
+ echo

---

From: Gregory A Lundberg <[email-masked]>
Date: Mon, 17 May 1999 13:01:01 -0400 (EDT)

> 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