Re: [HACKERS] Compile failure in CVS HEAD

2004-08-28 Thread Tom Lane
Devrim GUNDUZ <[EMAIL PROTECTED]> writes: > Latest CVS snapshot of 8.0.0 does not compile on Red Hat 9: > bison -y -d preproc.y > preproc.y:5383: warning: previous rule lacks an ending `;' > preproc.y:6367: fatal error: maximum table size (32767) exceeded You need a newer bison; or build from a

[HACKERS] Compile failure in CVS HEAD

2004-08-28 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Latest CVS snapshot of 8.0.0 does not compile on Red Hat 9: ln -s libecpg_compat.so.1.1 libecpg_compat.so make[4]: Leaving directory `/root/system/sources/pgsql/src/interfaces/ecpg/compatlib' make -C preproc

Re: [HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Euler Taveira de Oliveira
Hi Peter, > > > > I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol. > > > > How can we fix it? > > > > > > Put #ifdef CODESET around the offending code. > > > > OK. Another try. > > What does > > nl_langinfo(NULL) > > return? Probably not a valid codepage. > No. Just "". S

Re: [HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Peter Eisentraut
Euler Taveira de Oliveira wrote: > > > I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol. > > > How can we fix it? > > > > Put #ifdef CODESET around the offending code. > > OK. Another try. What does nl_langinfo(NULL) return? Probably not a valid codepage. -- Peter Eisentra

Re: [HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Euler Taveira de Oliveira
Hi Peter, > > I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol. > > How can we fix it? > > Put #ifdef CODESET around the offending code. > OK. Another try. -- Euler Taveira de Oliveira euler (at) ufgnet.ufg.br Desenvolvedor Web e Administrador de Sistemas UFGNet - Universidade

Re: [HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Andrew Dunstan
Tom Lane wrote: Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes: I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol. How can we fix it? 1) just define it on configure.in when we don't have it. Like this: You've got to be kidding. That will cause get_encoding_fro

Re: [HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Tom Lane
Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes: > I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol. > How can we fix it? > 1) just define it on configure.in when we don't have it. Like this: You've got to be kidding. That will cause get_encoding_from_locale to return some r

Re: [HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Peter Eisentraut
Euler Taveira de Oliveira wrote: > I am using an OpenBSD 3.5. OpenBSD doesn't have 'CODESET' symbol. > How can we fix it? Put #ifdef CODESET around the offending code. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)

[HACKERS] Compile failure on nl_langinfo

2004-07-31 Thread Euler Taveira de Oliveira
Hi, I am seeing the following compile failure in currrent CVS. gmake[4]: Leaving directory `/dados/pgsql/cvs/pgsql/src/port' gcc -O2 -fno-strict-aliasing -g -Wall -Wmissing-prototypes -Wmissing-declarations -DFRONTEND -I../../../src/interfaces/libpq -I../../../src/include -I/usr/local/include -

Re: [HACKERS] Compile failure in plperl

2004-07-04 Thread Andrew Dunstan
Ok. It's impossible for me to fix this by remote control - I need access to some box with one of these old versions of perl so I can come up with a clean solution. Or did you revert the change that put "#include ppport.h" in SPI.xs? cheers andrew Bruce Momjian wrote: Andrew Dunstan wrote: Tha

Re: [HACKERS] Compile failure in plperl

2004-07-04 Thread Bruce Momjian
Andrew Dunstan wrote: > > That is *intensely* annoying. What on earth are these function bodies > doing in a .h file anyway? (Remember, I just used the standard utility > to generate the file). > > Anyway, here is a version with all that stuff cut out - I don't believe > we need any of it. Doe

Re: [HACKERS] Compile failure in plperl

2004-07-04 Thread Bruce Momjian
Andrew Dunstan wrote: > > The problem is your old version of perl. > > Please see if the attached patch fixes it (The one I sent in previously > didn't apply cleanly - this one should). With your patch I now get this failure: gmake[4]: Leaving directory `/usr/var/local/src/gen

[HACKERS] Compile failure in plperl

2004-07-04 Thread Bruce Momjian
I am getting a CVS HEAD compile failure in plperl: gmake[4]: Leaving directory `/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/pl/tcl/modules' gmake[3]: Leaving directory `/usr/var/local/src/gen/pgsql/CURRENT/pgsql/src/pl/tcl' gmake[3]: Entering directory `/usr/v

Re: [HACKERS] Compile failure with SSL

2004-06-25 Thread Tom Lane
"Dave Page" <[EMAIL PROTECTED]> writes: > OK, looks like the error below is a Win32 thing. The patch attached > #ifdef'd out the permissions check on the private key file as it won't > work under Windows anyway (a similar check in postmaster.c has has > already been ifdef'd out for the same reason)

Re: [HACKERS] Compile failure with SSL

2004-06-22 Thread Dave Page
> -Original Message- > From: Merlin Moncure [mailto:[EMAIL PROTECTED] > Sent: 21 June 2004 15:40 > To: Dave Page > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: [HACKERS] Compile failure with SSL > > I had made the same changes as you to be_secure...

Re: [HACKERS] Compile failure with SSL

2004-06-21 Thread Merlin Moncure
Dave Page wrote: > OK, looks like the error below is a Win32 thing. The patch attached > #ifdef'd out the permissions check on the private key file as it won't > work under Windows anyway (a similar check in postmaster.c has has > already been ifdef'd out for the same reason). > > Incidently, the

Re: [HACKERS] Compile failure with SSL

2004-06-20 Thread Dave Page
19 June 2004 23:24 > To: [EMAIL PROTECTED] > Subject: [HACKERS] Compile failure with SSL > > I think this is another on of those 'might be Win32 specific' > problems. > When building on XP, with OpenSSL 0.9.7c (from the bitWalk > MinGW tools), I get the follow

[HACKERS] Compile failure with SSL

2004-06-19 Thread Dave Page
I think this is another on of those 'might be Win32 specific' problems. When building on XP, with OpenSSL 0.9.7c (from the bitWalk MinGW tools), I get the following failure: gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../src/include -I./src/include/port/w

Re: [HACKERS] compile failure on xmalloc()

2004-01-25 Thread Bruce Momjian
Neil Conway wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > I am seeing the following compile failure in currrent CVS. Seems there > > is a conflict between readline and psql's use of the xmalloc function > > name. > > This should be fixed in the latest CVS HEAD code (i.e. r1.82 of > commo

Re: [HACKERS] compile failure on xmalloc()

2004-01-25 Thread Neil Conway
Bruce Momjian <[EMAIL PROTECTED]> writes: > I am seeing the following compile failure in currrent CVS. Seems there > is a conflict between readline and psql's use of the xmalloc function > name. This should be fixed in the latest CVS HEAD code (i.e. r1.82 of common.c) -- can you make sure your so

[HACKERS] compile failure on xmalloc()

2004-01-24 Thread Bruce Momjian
I am seeing the following compile failure in currrent CVS. Seems there is a conflict between readline and psql's use of the xmalloc function name. --- gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-decla

Re: [HACKERS] compile failure with beta3 and --with-perl

2003-09-24 Thread Tom Lane
Robert Treat <[EMAIL PROTECTED]> writes: > Slackware 8.1, linux 2.4.18 i586, gcc version 2.95.3 20010315 (release) > This is perl, v5.6.1 built for i386-linux (is this too old?) Hm. On HPUX 10.20, I can report that CVS tip plperl seems to work with perl 5.8.0 (at least it can execute a simple fun

[HACKERS] compile failure with beta3 and --with-perl

2003-09-24 Thread Robert Treat
Slackware 8.1, linux 2.4.18 i586, gcc version 2.95.3 20010315 (release) This is perl, v5.6.1 built for i386-linux (is this too old?) parts from config.log configure:4214: checking for perl configure:4232: found /usr/local/bin/perl configure:4244: result: /usr/local/bin/perl configure:4253: checki

Re: [HACKERS] compile failure

2003-07-30 Thread Bruce Momjian
Someone at LinuxTag said they liked it because you can do the conversion in a text file, rather than compiling a conversion C file. --- Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Are we removing recode b

Re: [HACKERS] compile failure

2003-07-30 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Are we removing recode before going into beta? I was waiting for someone to holler that they really want it, but so far the silence is deafening ... regards, tom lane ---(end of broadcast)

Re: [HACKERS] compile failure

2003-07-30 Thread Bruce Momjian
Are we removing recode before going into beta? --- Greg Stark wrote: > > Is recode a feature that's normally enabled? > > ./configure '--enable-recode' '--enable-integer-datetimes' '--enable-debug' > '--with-perl' '--with

Re: [HACKERS] compile failure in hba.c

2003-07-22 Thread Tom Lane
Kurt Roeckx <[EMAIL PROTECTED]> writes: > In hba.c, line 1394 is missing two ) Yeah, my fault :-(. Should be fixed as of a few hours ago --- do you see any others? regards, tom lane ---(end of broadcast)--- TIP 7: don't for

[HACKERS] compile failure in hba.c

2003-07-22 Thread Kurt Roeckx
In hba.c, line 1394 is missing two ) if (pass == NULL) { ereport(LOG, (errmsg("local user with uid %d is not known to getpwuid", (int) peercred.uid);

Re: [HACKERS] compile failure

2003-07-20 Thread Bruce Momjian
If you add: #include to miscinit.c, does it compile with recode? Should I remove RECODE support? --- Greg Stark wrote: > > Is recode a feature that's normally enabled? > > ./configure '--enable-recode' '--enabl

Re: [HACKERS] compile failure in ecpg

2003-07-03 Thread Michael Meskes
On Wed, Jul 02, 2003 at 04:20:09PM -0400, Greg Stark wrote: > bash-2.05b$ flex -V > flex 2.5.31 I have 2.5.4. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De ICQ: 179140304, AIM: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use Postgre

Re: [HACKERS] Compile failure in ecpg/pgtypeslib/numeric.c

2003-07-03 Thread Michael Meskes
On Wed, Jul 02, 2003 at 11:49:25PM +0200, Kurt Roeckx wrote: > It seems someone removed some include files in revision 1.11 from > interfaces/ecpg/pgtypeslib/numeric.c. One of them was limits.h, > which is needed for INT_MAX and LONG_MAX. Hmm, I added postgres_fe.h and removed all includes that

Re: [HACKERS] compile failure in ecpg

2003-07-02 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: > Perhaps it's a bug in flex? I have: > bash-2.05b$ flex -V > flex 2.5.31 There's your problem. See http://fts.postgresql.org/db/msg.html?mid=1366520 Personally I'm still running 2.5.4 ... regards, tom lane --

Re: [HACKERS] Compile failure in ecpg/pgtypeslib/numeric.c

2003-07-02 Thread Bruce Momjian
#include readded. Thanks. --- Kurt Roeckx wrote: > It seems someone removed some include files in revision 1.11 from > interfaces/ecpg/pgtypeslib/numeric.c. One of them was limits.h, > which is needed for INT_MAX and LON

[HACKERS] Compile failure in ecpg/pgtypeslib/numeric.c

2003-07-02 Thread Kurt Roeckx
It seems someone removed some include files in revision 1.11 from interfaces/ecpg/pgtypeslib/numeric.c. One of them was limits.h, which is needed for INT_MAX and LONG_MAX. Readding it fixes it. Kurt ---(end of broadcast)--- TIP 5: Have you chec

Re: [HACKERS] compile failure in ecpg

2003-07-02 Thread Greg Stark
Michael Meskes <[EMAIL PROTECTED]> writes: > On Wed, Jul 02, 2003 at 02:00:49PM -0400, Greg Stark wrote: > > Ok, trying again with integer datetimes off and recode off it gets a bit > > further: > > What exactly was special on your site? This surely works for me. > > > pgc.c:3429: warning: no p

Re: [HACKERS] compile failure in ecpg

2003-07-02 Thread Michael Meskes
On Wed, Jul 02, 2003 at 02:00:49PM -0400, Greg Stark wrote: > Ok, trying again with integer datetimes off and recode off it gets a bit > further: What exactly was special on your site? This surely works for me. > pgc.c:3429: warning: no previous prototype for `yyget_lineno' > ... These are flex/

[HACKERS] compile failure in ecpg

2003-07-02 Thread Greg Stark
Ok, trying again with integer datetimes off and recode off it gets a bit further: /usr/bin//flex -o'pgc.c' pgc.l gcc -O0 -g -pg -DLINUX_PROFILE -g -Wall -Wmissing-prototypes -Wmissing-declarations -Wno-error -I./../include -I. -I../../../../src/include -DMAJOR_VERSION=3 -DMINOR_VERSION=0 -DP

Re: [HACKERS] compile failure

2003-07-02 Thread Kurt Roeckx
On Wed, Jul 02, 2003 at 10:39:11AM -0400, Greg Stark wrote: > > miscinit.c: In function `SetCharSet': > miscinit.c:205: structure has no member named `in' This is obviously something I overlooked. I'll see if I can fix it. Kurt ---(end of broadcast)---

Re: [HACKERS] compile failure

2003-07-02 Thread Greg Stark
Tom Lane <[EMAIL PROTECTED]> writes: > Greg Stark <[EMAIL PROTECTED]> writes: > > Now I'm getting > > timestamp.c: In function `tm2timestamp': > > timestamp.c:69: warning: implicit declaration of function `elog' > > timestamp.c:69: `ERROR' undeclared (first use in this function) > > I assume this

Re: [HACKERS] compile failure

2003-07-02 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: >> Now I'm getting >> timestamp.c: In function `tm2timestamp': >> timestamp.c:69: warning: implicit declaration of function `elog' >> timestamp.c:69: `ERROR' undeclared (first use in this function) >> I assume this is expected due to the error handling changes

Re: [HACKERS] compile failure

2003-07-02 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: > Now I'm getting > timestamp.c: In function `tm2timestamp': > timestamp.c:69: warning: implicit declaration of function `elog' > timestamp.c:69: `ERROR' undeclared (first use in this function) > I assume this is expected due to the error handling changes? No

Re: [HACKERS] compile failure

2003-07-02 Thread Greg Stark
Tom Lane <[EMAIL PROTECTED]> writes: > Greg Stark <[EMAIL PROTECTED]> writes: > > Is recode a feature that's normally enabled? > > Not by me --- wouldn't be the least bit surprised if it's broken. > Can you send a patch? Well my patch was to change --enable-recode to --disable-recode :) I'm not

Re: [HACKERS] compile failure

2003-07-02 Thread Tom Lane
Greg Stark <[EMAIL PROTECTED]> writes: > Is recode a feature that's normally enabled? Not by me --- wouldn't be the least bit surprised if it's broken. Can you send a patch? regards, tom lane ---(end of broadcast)--- TIP 8:

[HACKERS] compile failure

2003-07-02 Thread Greg Stark
Is recode a feature that's normally enabled? ./configure '--enable-recode' '--enable-integer-datetimes' '--enable-debug' '--with-perl' '--with-pam' '--with-openssl' '--with-gnu-ld' '--with-maxbackends=64' '--with-pgport=5432' 'CFLAGS=-O0 -g -pg -DLINUX_PROFILE' ... gcc -O0 -g -pg -DLINUX_PROFIL

Re: [HACKERS] compile failure on cvs tip --with-krb5

2003-06-24 Thread Bruce Momjian
Patch applied. Thanks. --- Kurt Roeckx wrote: > On Fri, Jun 20, 2003 at 07:48:02PM -0700, Joe Conway wrote: > > This change (I'm sure this will wrap poorly -- sorry): > > http://developer.postgresql.org/cvsweb.cgi/pgsql-se

Re: [HACKERS] compile failure on cvs tip --with-krb5

2003-06-23 Thread Bruce Momjian
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches I will try to apply it within the next 48 hours. --- Kurt Roeckx wrote: > On Fri, Jun 20, 2003

Re: [HACKERS] compile failure on cvs tip --with-krb5

2003-06-22 Thread Sean Chittenden
> > This change (I'm sure this will wrap poorly -- sorry): > > http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86 > > > > modified SockAddr, but no corresponding change was made here > > (fe-auth.c:612): > > > > case AUTH_REQ_KRB5: > > #ifde

Re: [HACKERS] compile failure on cvs tip --with-krb5

2003-06-21 Thread Joe Conway
Kurt Roeckx wrote: This patch should hopefully fix both kerberos 4 and 5. Thanks, the patch fixes the compile issue for me. Disclaimer: I can't vouch for krb4 at all. And, although I compile support for krb5, I do that to find build problems, not because I use krb5. So I can't really speak to t

Re: [HACKERS] compile failure on cvs tip --with-krb5

2003-06-21 Thread Kurt Roeckx
On Fri, Jun 20, 2003 at 07:48:02PM -0700, Joe Conway wrote: > This change (I'm sure this will wrap poorly -- sorry): > http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86 > > modified SockAddr, but no corresponding change was made here > (fe-aut

Re: [HACKERS] compile failure on cvs tip --with-krb5

2003-06-21 Thread Kurt Roeckx
On Fri, Jun 20, 2003 at 07:48:02PM -0700, Joe Conway wrote: > This change (I'm sure this will wrap poorly -- sorry): > http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86 > > modified SockAddr, but no corresponding change was made here > (fe-aut

[HACKERS] compile failure on cvs tip --with-krb5

2003-06-20 Thread Joe Conway
This change (I'm sure this will wrap poorly -- sorry): http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/libpq/pqcomm.h.diff?r1=1.85&r2=1.86 modified SockAddr, but no corresponding change was made here (fe-auth.c:612): case AUTH_REQ_KRB5: #ifdef KRB5 if (pg_krb5_sendauth(PQe

[HACKERS] compile failure in HEAD

2003-03-27 Thread Christopher Kings-Lynne
I seem to be getting this: gmake[3]: Entering directory `/home/chriskl/pgsql-temp/src/backend/parser' bison -y -d gram.y gram.y:4260.4-4307.10: type clash (`boolean' `keyword') on default action gram.y:4307.11: parse error, unexpected ":", expecting ";" or "|" gmake[3]: *** [parse.h] Error 1 Chr