Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > This would turn off the make failure when an old bison is called from
> > the makefile?
>
> Rephrase that as "this would give bison the right to fail of its own
> accord, rather than our prejudging its ability to cope."
>
> Given bis
Bruce Momjian <[EMAIL PROTECTED]> writes:
> This would turn off the make failure when an old bison is called from
> the makefile?
Rephrase that as "this would give bison the right to fail of its own
accord, rather than our prejudging its ability to cope."
Given bison's on-again-off-again track re
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I don't see a reason to have a flag to turn it off --- has anyone
> > reported that the version check failed?
>
> Since that version check has only been in CVS tip a month or two, and
> has not seen a release cycle, it'd be folly to t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I don't see a reason to have a flag to turn it off --- has anyone
> reported that the version check failed?
Since that version check has only been in CVS tip a month or two, and
has not seen a release cycle, it'd be folly to think it's bulletproof.
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I can see making a new bison required only when the version is *devel.
> > That way, folks testing CVS and even the *devel snapshots would need a
> > new bison, but our normal users wouldn't.
>
> Even then, if they're using a snapsho
an" <[EMAIL PROTECTED]>
Cc: "Markus Bertheau" <[EMAIL PROTECTED]>; "Larry Rosenman"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, July 01, 2003 7:10 PM
Subject: Re: [HACKERS] cvs build failure
> Bruce Momjian <[EMAIL PROTECTED]
В Срд, 02.07.2003, в 01:10, Alvaro Herrera пишет:
> On Wed, Jul 02, 2003 at 12:56:11AM +0200, Markus Bertheau wrote:
>
> > Maybe add a comment to the Makefile where bison is called that gives a
> > hint to the user in case bison fails.
>
> Not too many people read Makefiles these days
Sorry, I me
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I can see making a new bison required only when the version is *devel.
> That way, folks testing CVS and even the *devel snapshots would need a
> new bison, but our normal users wouldn't.
Even then, if they're using a snapshot they shouldn't need it.
P
On Wed, Jul 02, 2003 at 12:56:11AM +0200, Markus Bertheau wrote:
> But it seems weird to require a switch for the normal case, i.e. a
> tarball build, and not require it for a cvs build.
Yeah, I agree. Maybe the configure script should be built different for
the releases, so users downloading ta
В Срд, 02.07.2003, в 00:42, Tom Lane пишет:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Maybe make configure act as though bison is missing? Not sure. It
> >> seems like that could create unnecessary problems in other cases.
>
> > One trick would be to set YACC to some s
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Maybe make configure act as though bison is missing? Not sure. It
> >> seems like that could create unnecessary problems in other cases.
>
> > One trick would be to set YACC to some special value like
> > "bison
Larry Rosenman <[EMAIL PROTECTED]> writes:
> what version of bison are you using? I believe we require 1.875
> these days.
It would be nice to be able to say --without-ecpg at configure time.
Ecpg is the only part of pg that requires this version of bison and
and is not a core part of the projec
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Maybe make configure act as though bison is missing? Not sure. It
>> seems like that could create unnecessary problems in other cases.
> One trick would be to set YACC to some special value like
> "bison.too.old" and test for that wh
Usual installs don't need bison because the tarball has pregenerated
bison output files.
---
Alvaro Herrera wrote:
> On Tue, Jul 01, 2003 at 06:12:31PM -0400, Tom Lane wrote:
> >
> > I believe 'configure' will bleat about a
Tom Lane wrote:
> Markus Bertheau <[EMAIL PROTECTED]> writes:
> >> what version of bison are you using? I believe we require 1.875 these days.
>
> > 1.35. I'll upgrade. Thanks.
>
> I believe 'configure' will bleat about a too-old bison, but it won't
> refuse to proceed --- and the warning is eas
On Tue, Jul 01, 2003 at 06:12:31PM -0400, Tom Lane wrote:
>
> I believe 'configure' will bleat about a too-old bison, but it won't
> refuse to proceed --- and the warning is easy to miss in the pages of
> output that configure produces.
Maybe it should throw an error and refuse to continue if the
Markus Bertheau <[EMAIL PROTECTED]> writes:
>> what version of bison are you using? I believe we require 1.875 these days.
> 1.35. I'll upgrade. Thanks.
I believe 'configure' will bleat about a too-old bison, but it won't
refuse to proceed --- and the warning is easy to miss in the pages of
outp
CVS checks for an old bison, though it just throws a warning, not an
error.
---
Markus Bertheau wrote:
> ? ???, 01.07.2003, ? 21:41, Larry Rosenman ?:
> > what version of bison are you using? I believe we require 1.875
On Tue, Jul 01, 2003 at 09:39:59PM +0200, Markus Bertheau wrote:
> bison -y -d preproc.y
> preproc.y:6214: fatal error: maximum table size (32767) exceeded
> make[4]: *** [preproc.h] Error 1
> make[4]: Leaving directory
> `/home/bert/src/pgsql/src/interfaces/ecpg/preproc'
>
> What's the problem?
В Втр, 01.07.2003, в 21:41, Larry Rosenman пишет:
> what version of bison are you using? I believe we require 1.875 these days.
1.35. I'll upgrade. Thanks.
--
Markus Bertheau.
Berlin, Berlin.
Germany.
---(end of broadcast)---
TIP 8: explain analy
what version of bison are you using? I believe we require 1.875 these days.
LER
--On Tuesday, July 01, 2003 21:39:59 +0200 Markus Bertheau
<[EMAIL PROTECTED]> wrote:
Hi,
I'm trying to build cvs, but it fails:
bison -y -d preproc.y
preproc.y:6214: fatal error: maximum table size (32767) exce
Hi,
I'm trying to build cvs, but it fails:
bison -y -d preproc.y
preproc.y:6214: fatal error: maximum table size (32767) exceeded
make[4]: *** [preproc.h] Error 1
make[4]: Leaving directory
`/home/bert/src/pgsql/src/interfaces/ecpg/preproc'
What's the problem?
--
Markus Bertheau.
Berlin, Berl
22 matches
Mail list logo
