pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedbison
5+ messages / 4 participants
[nested] [flat]
* bison
@ 1999-10-11 19:52 Peter Eisentraut <peter_e@gmx.net>
0 siblings, 1 reply; 5+ messages in thread
From: Peter Eisentraut @ 1999-10-11 19:52 UTC (permalink / raw)
To: pgsql-docs; +Cc: pgsql-hackers@postgreSQL.org
You might want to include into the installation instructions (or whereever
it will end up) that GNU bison 1.25 is required. (right after the flex
stuff)
I have encountered problems in particular with the ecpg interface where
the Solaris yacc generated syntactically messed-up C code and bison 1.24
couldn't even process one of the .y files. (In case the ecpg maintainer is
unaware of this, let me know and I'll try to get a full problem
description. This happened with the CVS sources of today.)
This is just in addition to other problems that pop up once in a while
with vendor-supplied yaccs on the actual backend parser, I think.
-Peter
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] bison
@ 1999-10-12 05:43 Thomas Lockhart <lockhart@alumni.caltech.edu>
parent: Peter Eisentraut <peter_e@gmx.net>
0 siblings, 1 reply; 5+ messages in thread
From: Thomas Lockhart @ 1999-10-12 05:43 UTC (permalink / raw)
To: Peter Eisentraut <peter_e@gmx.net>; +Cc: pgsql-docs; pgsql-hackers@postgresql.org
> You might want to include into the installation instructions (or whereever
> it will end up) that GNU bison 1.25 is required. (right after the flex
> stuff)
We haven't been careful about building and shipping the bison output
in the tarball distribution, as we have for the main parser. It just
needs someone to look at it, as well as look at Jan's backend
languages which suffer from the same symptom as I recall...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] bison
@ 1999-10-12 14:36 Tom Lane <tgl@sss.pgh.pa.us>
parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 1999-10-12 14:36 UTC (permalink / raw)
To: Thomas Lockhart <lockhart@alumni.caltech.edu>; +Cc: Peter Eisentraut <peter_e@gmx.net>; pgsql-docs; pgsql-hackers@postgresql.org
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> You might want to include into the installation instructions (or whereever
>> it will end up) that GNU bison 1.25 is required. (right after the flex
>> stuff)
> We haven't been careful about building and shipping the bison output
> in the tarball distribution, as we have for the main parser.
Huh? src/tools/release_prep automatically builds both the main parser
and ecpg bison output files. Is there other stuff it should be
handling too?
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] bison
@ 1999-10-15 04:33 Thomas Lockhart <lockhart@alumni.caltech.edu>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Thomas Lockhart @ 1999-10-15 04:33 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Peter Eisentraut <peter_e@gmx.net>; pgsql-docs; pgsql-hackers@postgreSQL.org
> >> You might want to include into the installation instructions (or whereever
> >> it will end up) that GNU bison 1.25 is required. (right after the flex
> >> stuff)
> > We haven't been careful about building and shipping the bison output
> > in the tarball distribution, as we have for the main parser.
> Huh? src/tools/release_prep automatically builds both the main parser
> and ecpg bison output files. Is there other stuff it should be
> handling too?
afaik some of Jan's language stuff uses yacc also...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] bison
@ 1999-10-15 10:18 Jan Wieck <wieck@debis.com>
parent: Thomas Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 0 replies; 5+ messages in thread
From: wieck@debis.com @ 1999-10-15 10:18 UTC (permalink / raw)
To: lockhart@alumni.caltech.edu; +Cc: tgl@sss.pgh.pa.us; peter_e@gmx.net; pgsql-docs; pgsql-hackers@postgreSQL.org
>
> > >> You might want to include into the installation instructions (or whereever
> > >> it will end up) that GNU bison 1.25 is required. (right after the flex
> > >> stuff)
> > > We haven't been careful about building and shipping the bison output
> > > in the tarball distribution, as we have for the main parser.
> > Huh? src/tools/release_prep automatically builds both the main parser
> > and ecpg bison output files. Is there other stuff it should be
> > handling too?
>
> afaik some of Jan's language stuff uses yacc also...
Yepp - PL/pgSQL has it's own scanner/parser (i.e.
flex/bison). The tricky part in this case is that the
languages object file will be loaded at runtime into the
backend, where the main scanner/parser is already present.
Thus I'm mangling with sed(1) over the generated sources to
avoid global symbol conflicts.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck@debis.com (Jan Wieck) #
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~1999-10-15 10:18 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-10-11 19:52 bison Peter Eisentraut <peter_e@gmx.net>
1999-10-12 05:43 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-10-12 14:36 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-10-15 04:33 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-10-15 10:18 ` Jan Wieck <wieck@debis.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox