Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure does not (properly) check for yacc/bison #2784

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

configure does not (properly) check for yacc/bison #2784

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-03-07 16:17:07 +0100
From: @drstmane
To: buildtools devs <>
Version: 11.3.1 (Apr2011) [obsolete]

Last updated: 2011-05-31 13:59:26 +0200

Comment 15539

Date: 2011-03-07 16:17:07 +0100
From: @drstmane

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20110103 Fedora/3.6.13-1.fc14 Firefox/3.6.13
Build Identifier:

configure does not properly check for yacc/bison, or at least is does not disable SQL which requires yacc/bison for its parser.
Hence, if there is no yacc/bison configure finishes successfully, but compilation of SQL eventually fails.

Reproducible: Always

Steps to Reproduce:

  1. choose a system without yacc/bison
  2. configure MonetDB Mar2011 sources with sql enabled (default)
  3. (try to) compile

Actual Results:

make fails complaining about missing yacc/bison executable

Expected Results:

configure complains about missing yacc/bison and disables sql

Comment 15563

Date: 2011-03-11 14:00:12 +0100
From: @sjoerdmullender

I didn't realize that there was an open bug when I tried to fix this, otherwise I would have mentioned the bug number in the message.
Changeset http://dev.monetdb.org/hg/MonetDB/rev/da89d88f886d should contain the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant