ECPG and bison
Could anyone please tell me if we found a solution? It seems I missed
any discussion or whatsoever. The only things I know is that
postgresql.org still has bison 1.35 installed and 7.3 release is
nearing.
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
Yes, we are going to upgrade to bison 1.50 on our main server as soon as
Marc gets it installed. If you want to make your changes and commit
those now, you can, because I assume your bison 1.50 output will get
into CVS. I have bison 1.50 here too.
---------------------------------------------------------------------------
Michael Meskes wrote:
Could anyone please tell me if we found a solution? It seems I missed
any discussion or whatsoever. The only things I know is that
postgresql.org still has bison 1.35 installed and 7.3 release is
nearing.Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
--
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
On Fri, Oct 18, 2002 at 11:48:33AM -0400, Bruce Momjian wrote:
Yes, we are going to upgrade to bison 1.50 on our main server as soon as
Marc gets it installed. If you want to make your changes and commit
Okay.
those now, you can, because I assume your bison 1.50 output will get
into CVS. I have bison 1.50 here too.
The changes are there already, I just have to fold the ecpg.big branch
into HEAD.
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
Michael Meskes <meskes@postgresql.org> writes:
those now, you can, because I assume your bison 1.50 output will get
into CVS. I have bison 1.50 here too.
The changes are there already, I just have to fold the ecpg.big branch
into HEAD.
Probably you should refrain from doing that until Marc installs 1.50
at postgresql.org, else the nightly snapshots will be broken, to no
one's advantage.
Marc, can you do something about installing bison 1.50 soon?
(Guess I'd better get it loaded on my own machines, too...)
regards, tom lane
On Fri, 2002-10-18 at 13:51, Tom Lane wrote:
Michael Meskes <meskes@postgresql.org> writes:
those now, you can, because I assume your bison 1.50 output will get
into CVS. I have bison 1.50 here too.The changes are there already, I just have to fold the ecpg.big branch
into HEAD.Probably you should refrain from doing that until Marc installs 1.50
at postgresql.org, else the nightly snapshots will be broken, to no
one's advantage.Marc, can you do something about installing bison 1.50 soon?
(Guess I'd better get it loaded on my own machines, too...)
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).
LER
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Larry Rosenman wrote:
On Fri, 2002-10-18 at 13:51, Tom Lane wrote:
Michael Meskes <meskes@postgresql.org> writes:
those now, you can, because I assume your bison 1.50 output will get
into CVS. I have bison 1.50 here too.The changes are there already, I just have to fold the ecpg.big branch
into HEAD.Probably you should refrain from doing that until Marc installs 1.50
at postgresql.org, else the nightly snapshots will be broken, to no
one's advantage.Marc, can you do something about installing bison 1.50 soon?
(Guess I'd better get it loaded on my own machines, too...)
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).
I can confirm that:
Attached is the Changelog since 1.50.
--
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
Attachments:
Bruce Momjian <pgman@candle.pha.pa.us> writes:
Larry Rosenman wrote:
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).
I can confirm that:
http://ftp.gnu.org/gnu/bison/
Attached is the Changelog since 1.50.
Urgh. Nothing like major releases 2 weeks apart to give one a nice warm
comfy feeling about the stability of one's tools.
Offhand it looks like these are nearly all bug fixes, and so we'd better
standardize on 1.75 not 1.50. But I wonder what will be out next
week...
regards, tom lane
Peter Eisentraut wrote:
Michael Meskes writes:
Could anyone please tell me if we found a solution? It seems I missed
any discussion or whatsoever. The only things I know is that
postgresql.org still has bison 1.35 installed and 7.3 release is
nearing.I suggest that you merge your branch as soon as you are ready and force
the issue a bit. It's not like the bison installation on
postgresql.org can make the world stop.
Agreed. We need to push this.
--
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
Import Notes
Reply to msg id not found: Pine.LNX.4.44.0210181839460.928-100000@localhost.localdomain | Resolved by subject fallback
Michael Meskes writes:
Could anyone please tell me if we found a solution? It seems I missed
any discussion or whatsoever. The only things I know is that
postgresql.org still has bison 1.35 installed and 7.3 release is
nearing.
I suggest that you merge your branch as soon as you are ready and force
the issue a bit. It's not like the bison installation on
postgresql.org can make the world stop.
--
Peter Eisentraut peter_e@gmx.net
going to be dealing with this this weekend ... Bruce already asked me as
well, just been busy during the week, so had to defer to the weekend ...
if its not in place by tomorrow around, so, 8pm GMT,please feel free to
email-nag me :)
On Fri, 18 Oct 2002, Michael Meskes wrote:
Show quoted text
Could anyone please tell me if we found a solution? It seems I missed
any discussion or whatsoever. The only things I know is that
postgresql.org still has bison 1.35 installed and 7.3 release is
nearing.Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
On Fri, 18 Oct 2002, Tom Lane wrote:
Bruce Momjian <pgman@candle.pha.pa.us> writes:
Larry Rosenman wrote:
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).I can confirm that:
http://ftp.gnu.org/gnu/bison/
Attached is the Changelog since 1.50.Urgh. Nothing like major releases 2 weeks apart to give one a nice warm
comfy feeling about the stability of one's tools.Offhand it looks like these are nearly all bug fixes, and so we'd better
standardize on 1.75 not 1.50. But I wonder what will be out next
week...
that's one of hte reasons I've been holding off (the other being a busy
week) ... I *try* to keep stuff like this to what the FreeBSD ports
collection considers a stable release, and it hasn't been updated yet :(
On Fri, 2002-10-18 at 22:03, Marc G. Fournier wrote:
On Fri, 18 Oct 2002, Tom Lane wrote:
Bruce Momjian <pgman@candle.pha.pa.us> writes:
Larry Rosenman wrote:
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).I can confirm that:
http://ftp.gnu.org/gnu/bison/
Attached is the Changelog since 1.50.Urgh. Nothing like major releases 2 weeks apart to give one a nice warm
comfy feeling about the stability of one's tools.Offhand it looks like these are nearly all bug fixes, and so we'd better
standardize on 1.75 not 1.50. But I wonder what will be out next
week...that's one of hte reasons I've been holding off (the other being a busy
week) ... I *try* to keep stuff like this to what the FreeBSD ports
collection considers a stable release, and it hasn't been updated yet :(
The PR I referred to above is the PR to update to 1.75.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
On Fri, Oct 18, 2002 at 04:16:29PM -0400, Bruce Momjian wrote:
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).I can confirm that:
I just tried Marc's installation of 1.75 and compared the result with my
1.50 compiled version of ecpg grammar and found both .c files to be
identical. Seems the changes didn't effect the parser output.
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
Michael Meskes wrote:
On Fri, Oct 18, 2002 at 04:16:29PM -0400, Bruce Momjian wrote:
Looks like threre is a 1.75 out (based on a FreeBSD PR I just saw fly
by).I can confirm that:
I just tried Marc's installation of 1.75 and compared the result with my
1.50 compiled version of ecpg grammar and found both .c files to be
identical. Seems the changes didn't effect the parser output.
Oh, that's very good news. Makes me feel a little more secure.
--
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