On Tue, 17 Apr 2001, Lamar Owen wrote:
> I have built PostgreSQL 7.1 on a system with glibc-2.2 -- Red Hat 7.1.
> It works for me.
>
> There may be something else going onwith your system -- more details of
> your system configuration would be helpful.
> --
> Lamar Owen
> WGCR Internet Radio
>
On Tue, 17 Apr 2001, Tom Lane wrote:
> [EMAIL PROTECTED] 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 c
<[EMAIL PROTECTED]> writes:
> 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
>
<[EMAIL PROTECTED]> writes:
> 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
>
[EMAIL PROTECTED] wrote:
> This afternoon I download postgresql-7.1.tar.gz.
> After I extract this tarball,enter ./configure command to config this
> server.
> It was always blocked at the procedure of checking accept() function.
> After 5 hours of struggling I finally know the trouble source.
> T
[EMAIL PROTECTED] 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.
How about telling us what your problem is, rather than jump
YodaWu ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
What's wrong with glibc-devel-2.2
Long Description
This afternoon I download postgresql-7.1.tar.gz.
After I extract this tarball,enter ./configure command to config this
se
