From: | <yoda(at)cef(dot)org(dot)tw> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: What's wrong with glibc-devel-2.2 |
Date: | 2001-04-17 19:10:37 |
Message-ID: | Pine.LNX.4.21.0104180300360.14390-100000@ns.cef.org.tw |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, 17 Apr 2001, Tom Lane wrote:
> pgsql-bugs(at)postgresql(dot)org writes:
> > The version of my glibc is 2.2,but seems postgresql based on glibc 2.1.
>
> Say what? Postgres isn't dependent on any particular version of glibc;
> in fact it runs fine on many Unixen that don't use glibc at all.
After I change the version from 2.2 to 2.1 , this problem solved.
I think the key point is the define of accept() in 2.2.
accept() define in glibc 2.2
extern int accept (int __fd, __SOCKADDR_ARG __addr,
socklen_t *__restrict __addr_len)
__THROW;
Definition of __SOCKADDR_ARG in glibc 2.2
#if defined __cplusplus || !__GNUC_PREREQ (2, 7)
# define __SOCKADDR_ARG struct sockaddr *__restrict
# define __CONST_SOCKADDR_ARG __const struct sockaddr *
#else
Definition of __restrict in glibc 2.2
/* __restrict is known in EGCS 1.2 and above. */
#if !__GNUC_PREREQ (2,92)
# define __restrict /* Ignore */
#endif
Thank you for your asistance ....:)
>
> How about telling us what your problem is, rather than jumping to a
> conclusion about what caused it? What we want to see is exactly what
> commands you issued and exactly what error messages you got.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-04-17 20:45:50 | Re: What's wrong with glibc-devel-2.2 |
Previous Message | yoda | 2001-04-17 18:59:14 | Re: What's wrong with glibc-devel-2.2 |