mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Jörn Nettingsmeier  <nettings@folkwang-hochschule.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: yacc dependency of aic7xxx driver
Date: Wed, 07 Mar 2001 07:06:51 -0700	[thread overview]
Message-ID: <200103071406.f27E6pO25638@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Wed, 07 Mar 2001 12:48:30 +0100." <3AA6200E.8C398B2E@folkwang-hochschule.de>

>hello justin !
>
>i have just tried to install the latest 2.4.3pre3 kernel with your
>driver.
>it failed with yacc: file not found.
>while i could install yacc, i have never had to use it before. i was
>assuming that the newer bison could do the same thing (which is what
>i have installed).
>so far, the kernel has not relied on yacc, which is why i'd like to
>ask you if it's possible to make it work with bison.

The assembler makefile doesn't reference yacc, but instead relies
on gmake's built in rules to figure out how to generate a .c from
a .y.  I'm somewhat surprised that bison doesn't create a link to
yacc or that gmake doesn't try to look for bison.

Oh well.  We'll just have to be more careful in how future patches
are generated so that the dependency between the generated firmware
files and the firmware source only triggers if you are actually
performing firmware development.  Trying to build this simple
assmebler on everyone's systems is turning out to be just too
hard.

--
Justin

  reply	other threads:[~2001-03-07 14:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 11:48 Jörn Nettingsmeier
2001-03-07 14:06 ` Justin T. Gibbs [this message]
2001-03-07 14:42   ` Christoph Hellwig
2001-03-07 15:29     ` Justin T. Gibbs
2001-03-07 15:52       ` Richard B. Johnson
2001-03-07 16:12       ` Matti Aarnio
2001-03-07 18:54         ` Justin T. Gibbs
2001-03-07 16:46       ` Christoph Hellwig
2001-03-07 15:44   ` Jörn Nettingsmeier
2001-03-08  2:34     ` Peter Samuelson

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=200103071406.f27E6pO25638@aslan.scsiguy.com \
    --to=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nettings@folkwang-hochschule.de \
    /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

all inboxes | Powered by JetHome®