From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.4 failure to compile
Date: 17 May 2001 11:32:41 -0700 [thread overview]
Message-ID: <9e15g9$tcj$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010517132052.14991A-100000@chaos.analogic.com> <3B040C80.C2A7BC6@sun.com>
Followup to: <3B040C80.C2A7BC6@sun.com>
By author: Tim Hockin <thockin@sun.com>
In newsgroup: linux.dev.kernel
>
> The aic7xxx assembler requiring libdb1 is a bungle. Getting the headers
> for that right on various distros is not easy. Add to that it requires
> YACC, when most people have bison (yes, a shell script is easy to make, but
> not always an option).
>
Most people have both. However, if your distribution installs bison
and not yacc and does *NOT* install the "bison as yacc" wrapper, you
should complain to your distributor.
As far as "not always an option", that's ridiculous. If there really
isn't someone around who can install it globally, then put it in ~/bin
and set your PATH.
The command "yacc" should be expected to work. This is as insane as
the flamage in the cdrecord documentation about Linux installing GNU
make as "make".
-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:33 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 [this message]
2001-05-17 18:47 ` Richard B. Johnson
2001-05-17 18:52 ` H. Peter Anvin
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='9e15g9$tcj$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 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.