Bug 812 - alphaev7-dec-osf5.1 cc compiler warning for OpenSSH-3.8p1
Summary: alphaev7-dec-osf5.1 cc compiler warning for OpenSSH-3.8p1
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: 3.8p1
Hardware: Alpha OSF/1
: P2 trivial
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-10 20:26 AEDT by Joerg Schulenburg
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:

Attachments
#undef getaddrinfo if defined (637 bytes, patch)
2004-03-10 20:39 AEDT, Darren Tucker 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schulenburg 2004-03-10 20:26:34 AEDT 
cc generates lot of warnings with same message:
cc: Warning: openbsd-compat/fake-rfc2553.h, line 136: The redefinition of the
macro "getaddrinfo" conflicts with a current definition because the number of
parameters is different.  The redefinition is now in effect. (macroredef)
#define getaddrinfo(a,b,c,d)    (ssh_getaddrinfo(a,b,c,d))
--------------------^
Comment 1 Darren Tucker 2004-03-10 20:31:15 AEDT 
What's the system's definition of the getaddrinfo macro?  Does adding "#undef
getaddrinfo" before "#define getaddrinfo(a,b,c,d)" silence the warnings?
Comment 2 Darren Tucker 2004-03-10 20:39:06 AEDT 
Created attachment 571 [details]
#undef getaddrinfo if defined

Please try this patch
Comment 3 Joerg Schulenburg 2004-03-10 20:49:35 AEDT 
I found a getaddrinfo definition in /usr/include/netdb.h using grep getaddrinfo
 /usr/include/*.h, but I dont understand
if that definition is connected with the problem. 
Here is an excerpt of netdb.h:
#if defined (_SOCKADDR_LEN) || defined (_XOPEN_SOURCE_EXTENDED)
#define getaddrinfo ngetaddrinfo
#else
#define getaddrinfo ogetaddrinfo
#endif
#ifdef _OSF_SOURCE
extern int getaddrinfo __((const char *, const char *, const struct addrinfo *,
                           struct addrinfo **));

Nevertheless, an undef getaddrinfo solves the problem.
Comment 4 Darren Tucker 2004-03-10 21:13:20 AEDT 
It appears Tru64 has 2 library calls for getaddrinfo (ogetaddrinfo and
ngetaddrinfo) that presumably behave differently in some circumstances.  

(Aside: I wonder if those differences are responsible for the strange
getaddrinfo problems we've seen on Tru64?)

Anyway, it has been fixed (attachment #571 [details]) for the next release.  Thanks for
the report.
Comment 5 Damien Miller 2004-04-14 12:24:20 AEST 
Mass change of RESOLVED bugs to CLOSED