Bruce,
On Mon, Jun 23, 2003 at 09:50:49PM -0400, Bruce Momjian wrote:
> OK, patch applied to typedef sa_family_t for cygwin. If other
> platforms need it, I will have to do something more generic.
I'm happy to report that the above patch solves one of Cygwin's current
build problems. However, C
OK, patch applied to typedef sa_family_t for cygwin. If other platforms
need it, I will have to do something more generic.
Thanks for the testing. Block removed, though I did have that ISP
marked as cronic, so there must have been a bunch of spam from there,
not just a few.
---
deststar wrote:
> I still seem to get a compile problem (included below).
> Will double check tomorrow when not so tired (02:15 here).
> Cheers,
> - Stuart
> P.S. My server seems to be blacklisted as a spam server by you. Please
> could you white list me.
>
> gcc -O2 -g -Wall -Wmissing-prototypes
I still seem to get a compile problem (included below).
Will double check tomorrow when not so tired (02:15 here).
Cheers,
- Stuart
P.S. My server seems to be blacklisted as a spam server by you. Please
could you white list me.
gcc -O2 -g -Wall -Wmissing-prototypes -Wmissing-declarations
-I../..
You might still have a problem with compiling getaddrinfo.c. Please let
me know and I can correct it.
---
deststar wrote:
> On cygwin sa_family_t was undeclared, adding the following line:
> typedef unsigned short sa_family
OK, I just applied a patch which should fix cygwin too. Please give it
a try. Thanks.
---
deststar wrote:
> Yes there's:
> struct sockaddr {
>unsigned short sa_family; /* address family, AF_xxx */
>c
Yes there's:
struct sockaddr {
unsigned shortsa_family; /* address family, AF_xxx */
char sa_data[14];/* 14 bytes of protocol address */
};
in socket.h
struct sockaddr {
u_short sa_family;
charsa_data[14];
};
in winsock.h & winsock2.h
deststar, is there any sa_family or ss_family in the cygwin include
directory, perhap with double leading underscores?
---
deststar wrote:
> Jason Tishler wrote:
> > On Sun, Jun 15, 2003 at 04:54:21PM +0100, deststar wrote:
Sorry didn't see it (& still can't in my inbox - where was it sent?)
Mine was a hack based on reading that sa_family_t should be 16 bits (in
RFC 2553 IIRC) to solve a cygwin specific problem.
If you have a general solution then that is much better than mine
thank you,
- Stuart
Bruce Momjian wrote
I am confused why you didn't like the following patch I posted, which
pulls the family data type length right out of the structure, rather than
having to configure it for every OS that doesn't have sa_family_t?
---
deststar
Jason Tishler wrote:
On Sun, Jun 15, 2003 at 04:54:21PM +0100, deststar wrote:
On cygwin sa_family_t was undeclared, adding the following line:
typedef unsigned short sa_family_t;
to both:
src/port/getaddrinfo.c
src/include/libpq/pqcomm.h
Isn't the attached or fixing Cygwin itself a better appro
On Sun, Jun 15, 2003 at 04:54:21PM +0100, deststar wrote:
> On cygwin sa_family_t was undeclared, adding the following line:
> typedef unsigned short sa_family_t;
> to both:
> src/port/getaddrinfo.c
> src/include/libpq/pqcomm.h
Isn't the attached or fixing Cygwin itself a better approach?
> seeme
On cygwin sa_family_t was undeclared, adding the following line:
typedef unsigned short sa_family_t;
to both:
src/port/getaddrinfo.c
src/include/libpq/pqcomm.h
seemed to compile ok but with make check there was one regression
failure in test privileges (doesn't look realted, but I'm not sure).
Als
13 matches
Mail list logo
