Christine Kluka <[EMAIL PROTECTED]> writes:
> When installing Postgres 7.1rc4 on Solaris 7, I get the following error
> on make:
> gcc -Wall -Wmissing-prototypes -Wmissing-declarations
> -I../../../../src/include
>-c filename.c -o filename.o
That is not an error message; it looks like a perf
When installing Postgres 7.1rc4 on Solaris 7, I get the following error
on make:
gcc -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../../src/include
-c filename.c -o filename.o
I can't do a regression test -there is no pgsql folder in /usr/src - and
of course createdb doesn't work
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
>
David George <[EMAIL PROTECTED]> writes:
> I just built the postgresql 7.1 final and the configure script is still
> checking for sfio. Not a major big deal, but I need to remove the sfio
> check from configure.in, run autoconf, and then configure to fix it. If
> you remember sfio on Sparc Solar
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
>
Hi Postgres-people,
in the linux rc script for (start|stop)ing postgres
a comment says to add the following lines to the postgres
users' .bash_profile:
PATH=$PATH:$HOME/bin
MANPATH=$MANPATH:/opt/pgsql/man
PGLIB=/opt/pgsql/lib
PGDATA=/opt/pgsql/data
There
I want to thank you for the excellent and fast responses I have received
in the past. Especially while troubleshooting the sfio problem. These
problems are VERY minor and easily worked around. Part of the reason I
am posting them is just in case someone else runs across the same
things. I am r
<[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
Dave Cramer ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC setObject(n,obj) throws exception when obj is null
Long Description
The jdbc call setObject(n,obj) does not set the column to null if the object is null
and the
13 matches
Mail list logo
