Re: [PORTS] Compiling on 8.1.3 on Openserver 5.05

Mark Campbell <[email protected]> Thu, 11 May 2006 17:20:52 +0200
Newsgroups gmane.comp.db.postgresql.ports
Message-ID <[email protected]>
Searching through /usr/include with the following script:

for i in `find . *`
do
   egrep "htonl|htons|ntohs" $i
   if [ $? = 0 ]
   then
      echo $i
   fi
done

I found the following:

extern u_short  mdi_htons(u_short);
extern u_short  mdi_ntohs(u_short);
in /usr/include/sys/mdi.h

u_long ntohl __P((u_long)), htonl __P((u_long));
u_short ntohs __P((u_short)), htons __P((u_short));
#define htonl(x)        (x)
#define ntohs(x)        (x)
#define htons(x)        (x)
in /usr/include/sys/byteorder.h

#define IXDR_PUT_LONG(buf, v)           (*(buf)++ = (long)htonl((ulong)v))
in /usr/include/rpc/xdr.h

Nothing was found in /usr/local/include

The problem I had with configure, was that gcc could not find cc1

Mark Campbell

Confidentiality Notice: http://ucs.co.za/conf.html



Tom Lane wrote:
> Mark Campbell <[email protected]> writes:
>   
>> getaddrinfo.c: In function `pg_getaddrinfo':
>> getaddrinfo.c:189: warning: implicit declaration of function `htonl'
>> getaddrinfo.c:211: `h_errno' undeclared (first use in this function)
>> getaddrinfo.c:211: (Each undeclared identifier is reported only once
>> getaddrinfo.c:211: for each function it appears in.)
>> getaddrinfo.c:215: warning: unreachable code at beginning of switch 
>> statement
>> getaddrinfo.c:238: warning: implicit declaration of function `htons'
>> getaddrinfo.c: In function `pg_getnameinfo':
>> getaddrinfo.c:416: warning: implicit declaration of function `ntohs'
>>     
>
> Hmm, looks like your system declares htonl() and friends in some other
> header file than where getaddrinfo.c is expecting.  Grep through
> everything under /usr/include and see where these symbols are declared.
>
> BTW, what problems did you have with configure?
>
> 			regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
>