From: "H. Peter Anvin" <hpa@transmeta.com>
To: root@chaos.analogic.com
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.4 failure to compile
Date: Thu, 17 May 2001 11:52:54 -0700 [thread overview]
Message-ID: <3B041E06.BF5155ED@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010517144217.2854A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
>
> I have both. I also have `flex`, but not `lex'. `lex' is a simlink to
> flex. What this compile wanted is some header files in expects for
> `yacc` that are not present. And they don't come with the `bison`
> distribution. Maybe they came with `yacc` years ago? Anyway there
> are some poor assumptions being made in the source Makefile.
>
> It would be nice to have the 'microcode' assembler running for
> aic7xxx since it is now required for the thing to load.
>
It worked just fine with "bison" here (with the appropriate shell script
added.)
I think the header file you're talking about is the db1 header file,
which has nothing to do with yacc -- it's the Berkeley libdb version 1,
which is a pretty bad thing to require.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-05-17 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 17:23 Linux-2.4.4 failure to compile Richard B. Johnson
2001-05-17 17:38 ` Tim Hockin
2001-05-17 18:03 ` Christoph Hellwig
2001-05-17 18:32 ` H. Peter Anvin
2001-05-17 18:47 ` Richard B. Johnson
2001-05-17 18:52 ` H. Peter Anvin [this message]
2001-05-18 6:32 ` Lorenzo Marcantonio
2001-05-18 10:41 ` Anuradha Ratnaweera
2001-05-19 12:16 ` David Weinehall
-- strict thread matches above, loose matches on Subject: below --
2001-05-17 18:33 Cress, Andrew R
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=3B041E06.BF5155ED@transmeta.com \
--to=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.