public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: linux@bucksch.org
To: gcc-gnats@gcc.gnu.org
Subject: other/2529: configure doesn't check for bison
Date: Tue, 10 Apr 2001 18:36:00 -0000	[thread overview]
Message-ID: <20010411013525.11448.qmail@sourceware.cygnus.com> (raw)

>Number:         2529
>Category:       other
>Synopsis:       configure doesn't check for bison
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 10 18:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Ben Bucksch
>Release:        gcc-20010402
>Organization:
>Environment:

>Description:
Tried to compile 2001-04-02 gcc 3.0 snapshot. Standard options: |../gcc-source/configure --enable-threads --enable-shared; make bootstrap|.

I didn't have bison installed.

configure worked, as far I as I could see, but compilation quickly (after 30 seconds or so) failed with missing files (see below). After I installed bison, it worked fine.

Last lines of make output:
(cd ../../gcc-20010402/gcc/java && \
false -t --name-prefix=java_ -o p$$.c parse.y && \
mv -f p$$.c parse.c)
make[2]: *** [../../gcc-20010402/gcc/java/parse.c] Error 1
>How-To-Repeat:
(guessed)
1. Rename the bison executable of your system.
2. Extract gcc3.0 snapshot, configure (in separate bin dir), make bootstrap.
>Fix:
(proposed)
Check for existance of bison in configure. Bail, if not found.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-04-10 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 18:36 linux [this message]
2002-05-16 18:35 rth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010411013525.11448.qmail@sourceware.cygnus.com \
    --to=linux@bucksch.org \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).