Re: Unixware 713 probs

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: ohp(at)pyrenet(dot)fr, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unixware 713 probs
Date: 2003-09-07 19:57:29
Message-ID: 265850000.1062964649@lerlaptop.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

--On Sunday, September 07, 2003 12:52:18 -0700 Stephan Szabo
<sszabo(at)megazone(dot)bigpanda(dot)com> wrote:

>
> On Sun, 7 Sep 2003, Larry Rosenman wrote:
>
>>
>>
>> --On Sunday, September 07, 2003 20:22:30 +0200 ohp(at)pyrenet(dot)fr wrote:
>>
>> [snip]
>>
>> > /usr/local/bin/gmake -C libpq all
>> > gmake[3]: Entering directory `/home/postgres/pgsql/src/backend/libpq'
>> > cc -O -Kinline,no_host -I../../../src/include -I/usr/local/include -c
>> > -o ip.o ip.c UX:acomp: ERROR: "ip.c", line 416: Syntax error before or
>> > at: . UX:acomp: WARNING: "ip.c", line 419: left operand of "." must be
>> > struct/union object UX:acomp: WARNING: "ip.c", line 427: left operand
>> > of "." must be struct/union object UX:acomp: WARNING: "ip.c", line
>> > 428: left operand of "." must be struct/union object UX:acomp:
>> > WARNING: "ip.c", line 429: left operand of "." must be struct/union
>> > object UX:acomp: WARNING: "ip.c", line 430: left operand of "." must
>> > be struct/union object UX:acomp: ERROR: "ip.c", line 451: Syntax error
>> > before or at: . UX:acomp: ERROR: "ip.c", line 452: invalid type
>> > combination
>> > UX:acomp: WARNING: "ip.c", line 455: left operand of "." must be
>> > struct/union object UX:acomp: WARNING: "ip.c", line 464: left operand
>> > of "." must be struct/union object UX:acomp: WARNING: "ip.c", line
>> > 465: left operand of "." must be struct/union object UX:acomp:
>> > WARNING: "ip.c", line 466: left operand of "." must be struct/union
>> > object UX:acomp:
>> line 416 is:
>>
>> int32 s_addr;
>>
>> s_addr is seen by the compiler as:
>>
>> uint32 __S_un . __S_addr ;
>>
>>
>> We need to pick another name.
>
> As a side note, if s_addr is being defined by a common system header, you
> should probably complain to your vendor as well, since that's amazingly
> bad behavior on its part.

netinet/in_f.h:#define s_addr __S_un.__S_addr

Hrm. I'll ask, but this is SCO, so.........

Meanwhile, this header is in the field, so.........
I fired off a note to a contact at SCO.

LER

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2003-09-07 19:59:32 Re: Does "vacuum analyze" contain "vacuum"?
Previous Message Stephan Szabo 2003-09-07 19:52:18 Re: Unixware 713 probs

Browse pgsql-hackers by date

  From Date Subject
Next Message Nailah Ogeer 2003-09-07 20:05:59 Code insertion
Previous Message Stephan Szabo 2003-09-07 19:52:18 Re: Unixware 713 probs

Browse pgsql-patches by date

  From Date Subject
Next Message Nailah Ogeer 2003-09-07 20:05:59 Code insertion
Previous Message Stephan Szabo 2003-09-07 19:52:18 Re: Unixware 713 probs