Thread: problems with building recent cvs snaphots

problems with building recent cvs snaphots

From
Hubert depesz Lubaczewski
Date:
hi
when i'm trying to build recent cvs snaphots (taken 30 minuts ago for
example, but i had the same problem with eariel snapshots as well), i
get this (after configure, during make:
$ make maintainer-clean && ./depesz.configure.sh && make
...
...
gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -shared
-Wl,-soname,libecpg.so.3 execute.o typename.o descriptor.o data.o
error.o prepare.o memory.o connect.o misc.o
-L../../../../src/interfaces/libpq -lpq
-Wl,-rpath,/home/users/pgdba/work/lib -o libecpg.so.3.4.0
rm -f libecpg.so.3
ln -s libecpg.so.3.4.0 libecpg.so.3
rm -f libecpg.so
ln -s libecpg.so.3.4.0 libecpg.so
make[4]: Leaving directory
`/home/users/pgdba/cvs/pgsql/src/interfaces/ecpg/lib'
make -C preproc all
make[4]: Entering directory
`/home/users/pgdba/cvs/pgsql/src/interfaces/ecpg/preproc'
make -C ../../../../src/port all
make[5]: Entering directory `/home/users/pgdba/cvs/pgsql/src/port'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory `/home/users/pgdba/cvs/pgsql/src/port'
bison -y -d  preproc.y
preproc.y:5560: fatal error: maximum table size (32767) exceeded
make[4]: *** [preproc.h] Error 1
make[4]: Leaving directory
`/home/users/pgdba/cvs/pgsql/src/interfaces/ecpg/preproc'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/users/pgdba/cvs/pgsql/src/interfaces/ecpg'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/users/pgdba/cvs/pgsql/src/interfaces'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/users/pgdba/cvs/pgsql/src'
make: *** [all] Error 2

$

depesz.configure.sh is my configure script which calls ./configure with
appropiate parameters:
$ cat depesz.configure.sh
#!/bin/bash
./configure \
        --prefix=/home/users/pgdba/work \
        --with-tcl \
        --with-tk \
        --with-perl \
        --with-python \
        --without-java \
        --without-krb4 \
        --without-krb5 \
        --without-pam \
        --without-openssl \
        --with-readline \
        --with-zlib \
        --with-gnu-ld

versions of my software:
$ rpm -q gcc glibc readline perl python bison flex cpp autoconf automake
libtool zlib | sort
autoconf-2.53a-1
automake-1.6.3-1
bison-1.35-5
cpp-2.95.4-0.20010823.3
flex-2.5.4a-27
gcc-2.95.4-0.20010823.3
glibc-2.2.5-21
libtool-1.4.2-12
perl-5.6.1-63
python-2.2.1-19
readline-4.3-5
zlib-1.1.4-5

what should i do?

depesz

--
hubert depesz lubaczewski                          http://www.depesz.pl/
------------------------------------------------------------------------
Mój Boże, spraw abym milczał, dopóki się nie upewnię,  że  naprawdę  mam
coś do powiedzenia.                                      (c) 1998 depesz


Re: problems with building recent cvs snaphots

From
Doug McNaught
Date:
Hubert depesz Lubaczewski <depesz@depesz.pl> writes:

> hi
> when i'm trying to build recent cvs snaphots (taken 30 minuts ago for
> example, but i had the same problem with eariel snapshots as well), i
> get this (after configure, during make:

Upgrade your Bison to 1.50 or later (1.75 is current).

-Doug

Re: problems with building recent cvs snaphots

From
Tom Lane
Date:
Hubert depesz Lubaczewski <depesz@depesz.pl> writes:
> bison -y -d  preproc.y
> preproc.y:5560: fatal error: maximum table size (32767) exceeded

> what should i do?

Update to bison 1.50 or later (1.75 is current last I checked).
Or use a tarball distribution (beta3 or the nightly snapshot).

            regards, tom lane

Re: problems with building recent cvs snaphots

From
Hubert depesz Lubaczewski
Date:
On Fri, Nov 01, 2002 at 07:28:16PM -0500, Tom Lane wrote:
> Update to bison 1.50 or later (1.75 is current last I checked).

i can't update - it's not supported by my distribution.

> Or use a tarball distribution (beta3 or the nightly snapshot).

and precompiled binaries are not really an option.

depesz

--
hubert depesz lubaczewski                          http://www.depesz.pl/
------------------------------------------------------------------------
Mój Boże, spraw abym milczał, dopóki się nie upewnię,  że  naprawdę  mam
coś do powiedzenia.                                      (c) 1998 depesz


Re: problems with building recent cvs snaphots

From
Hubert depesz Lubaczewski
Date:
On Fri, Nov 01, 2002 at 07:23:40PM -0500, Doug McNaught wrote:
> Upgrade your Bison to 1.50 or later (1.75 is current).

unfortunatelly the linux distribution i use doesn't provide it. as far
as i know it's because bison > 1.35 is not compatibile with gcc 3.2.

can i do anything with bison 1.35?=20

depesz

--=20
hubert depesz lubaczewski                          http://www.depesz.pl/
------------------------------------------------------------------------
M=F3j Bo=BFe, spraw abym milcza=B3, dop=F3ki si=EA nie upewni=EA,  =BFe  na=
prawd=EA  mam
co=B6 do powiedzenia.                                      (c) 1998 depesz

Re: problems with building recent cvs snaphots

From
Doug McNaught
Date:
Hubert depesz Lubaczewski <depesz@depesz.pl> writes:

> On Fri, Nov 01, 2002 at 07:28:16PM -0500, Tom Lane wrote:
> > Update to bison 1.50 or later (1.75 is current last I checked).
>
> i can't update - it's not supported by my distribution.
>
> > Or use a tarball distribution (beta3 or the nightly snapshot).
>
> and precompiled binaries are not really an option.

Tom means a tarball source distribution.  You don't have to run Bison
when building from a tarball (the Bison-generated files are already
included); you do when building from CVS.  Clear?

-Doug

Re: problems with building recent cvs snaphots

From
Tom Lane
Date:
Doug McNaught <doug@mcnaught.org> writes:
> Hubert depesz Lubaczewski <depesz@depesz.pl> writes:
>> On Fri, Nov 01, 2002 at 07:28:16PM -0500, Tom Lane wrote:
>>> Or use a tarball distribution (beta3 or the nightly snapshot).
>>
>> and precompiled binaries are not really an option.

> Tom means a tarball source distribution.  You don't have to run Bison
> when building from a tarball (the Bison-generated files are already
> included); you do when building from CVS.  Clear?

Also, if you're willing to build Postgres from source, I fail to see why
you're resisting building bison from source.  It's not hard:

    tar xfz bison-1.75.tar.gz
    cd bison-1.75
    make
    make check    -- optional
    make install    -- probably need to do this step as root

and then make sure /usr/local/bin is in your PATH ahead of whereever
the standard bison lives.  When your distro updates, clean out
/usr/local and you're back to normal.

            regards, tom lane

Re: problems with building recent cvs snaphots

From
Tom Lane
Date:
Hubert depesz Lubaczewski <depesz@depesz.pl> writes:
> unfortunatelly the linux distribution i use doesn't provide it. as far
> as i know it's because bison > 1.35 is not compatibile with gcc 3.2.

Nonsense.  I installed bison 1.75 just yesterday on a fresh RH 8.0
installation (which is gcc 3.2).  Works fine.

            regards, tom lane

Re: problems with building recent cvs snaphots

From
Hubert depesz Lubaczewski
Date:
On Sat, Nov 02, 2002 at 09:13:23AM -0500, Doug McNaught wrote:
> Tom means a tarball source distribution.  You don't have to run Bison
> when building from a tarball (the Bison-generated files are already
> included); you do when building from CVS.  Clear?

aaa. sorry. i misunderstood. i'll look at this.

depesz

--
hubert depesz lubaczewski                          http://www.depesz.pl/
------------------------------------------------------------------------
Mój Boże, spraw abym milczał, dopóki się nie upewnię,  że  naprawdę  mam
coś do powiedzenia.                                      (c) 1998 depesz