plpgsql compile failure

Started by Bruce Momjianabout 23 years ago4 messageshackers

bruce@momjian.us

about 23 years ago

I am seeing the following plpgsql compile failure in CVS:

#$ gmake
bison -y -d gram.y
NONE:0: /usr/contrib/bin/gm4: ERROR: EOF in string
sed -e 's/yy/plpgsql_yy/g' -e 's/YY/PLPGSQL_YY/g' < y.tab.c >
./pl_gram.c
/bin/sh: cannot open y.tab.c: no such file
gmake: *** [pl.tab.h] Error 2

I believe it is related to this commit:

revision 1.41
date: 2003/03/25 03:16:40; author: tgl; state: Exp; lines: +29 -6
plpgsql can assign to subscripted variables now, e.g.
x[42] := whatever;
The facility is pretty primitive because it doesn't do array slicing and
it has the same semantics as array update in SQL (array must already
be non-null, etc). But it's a start.

I have attached the change --- anyone see the cause? I have bison 1.75.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Joe Conway

mail@joeconway.com

about 23 years ago

In reply to: Bruce Momjian (#1)

Re: plpgsql compile failure

Bruce Momjian wrote:

I am seeing the following plpgsql compile failure in CVS:

#$ gmake
bison -y -d gram.y
NONE:0: /usr/contrib/bin/gm4: ERROR: EOF in string
sed -e 's/yy/plpgsql_yy/g' -e 's/YY/PLPGSQL_YY/g' < y.tab.c >
./pl_gram.c
/bin/sh: cannot open y.tab.c: no such file
gmake: *** [pl.tab.h] Error 2

I believe it is related to this commit:

I'm seeing the same thing, and I also have bison 1.75. I confirmed that
by reverting the commit, the problem goes away. Possibly bison version
related?

Joe

Tom Lane

tgl@sss.pgh.pa.us

about 23 years ago

In reply to: Joe Conway (#2)

Re: plpgsql compile failure

Joe Conway <mail@joeconway.com> writes:

Bruce Momjian wrote:

I am seeing the following plpgsql compile failure in CVS:

I'm seeing the same thing, and I also have bison 1.75.

Considering how trivial the grammar change is, it's hard to call this
anything except a bison bug. I'd be interested to know what causes it
though --- is it worth trying to invent a workaround so people don't
have to upgrade?

regards, tom lane

Bruce Momjian

bruce@momjian.us

about 23 years ago

In reply to: Tom Lane (#3)

Re: plpgsql compile failure

Tom Lane wrote:

Joe Conway <mail@joeconway.com> writes:

Bruce Momjian wrote:

I am seeing the following plpgsql compile failure in CVS:

I'm seeing the same thing, and I also have bison 1.75.

Considering how trivial the grammar change is, it's hard to call this
anything except a bison bug. I'd be interested to know what causes it
though --- is it worth trying to invent a workaround so people don't
have to upgrade?

Not worth the effort -- email posted requiring 1.85.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

plpgsql compile failure

Attachments: