From: jhpb@sarto.gaithersburg.md.us (Joseph H. Buehler)
To: egcs@cygnus.com
Subject: Re: bison, SCO OSR 5.0.4
Date: Mon, 19 Jan 1998 23:51:00 -0000 [thread overview]
Message-ID: <m2ra64kq2e.fsf@altera.gaithersburg.md.us> (raw)
In-Reply-To: <19980118191439.64718@jpr.com>
Jean-Pierre Radley <jpr@jpr.com> writes:
> I've done 'make bootstrap' on several different egcs snapshots, and did
> so again yesterday after collecting yesterday's code with cvs.
>
> Having picked up today's updates with cvs, I again ran configure and
> this time just typed 'make'. It barfed on not finding bison on my
> system (SCO OpenServer 5.0.4)
>
> So I installed bison and the compilation is proceeding, but why would
> yacc suffice for 'make bootstrap', but not for just 'make'?
It looks to me as though cvs pulls everything out in alphabetical
order, and puts the current time on the files. This will undoubtedly
cause some interesting results when you run make, because some of the
files under cvs are generated files.
Joe Buehler
prev parent reply other threads:[~1998-01-19 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-18 21:51 Jean-Pierre Radley
1998-01-19 23:51 ` Joseph H. Buehler [this message]
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=m2ra64kq2e.fsf@altera.gaithersburg.md.us \
--to=jhpb@sarto.gaithersburg.md.us \
--cc=egcs@cygnus.com \
/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).