The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jörn Nettingsmeier  <nettings@folkwang-hochschule.de>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: yacc dependency of aic7xxx driver
Date: Wed, 07 Mar 2001 16:44:45 +0100	[thread overview]
Message-ID: <3AA6576D.81501D0@folkwang-hochschule.de> (raw)
In-Reply-To: <200103071406.f27E6pO25638@aslan.scsiguy.com>

"Justin T. Gibbs" wrote:
> 
> >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.

i might also be SuSE 7.1 related, since this was the first kernel i
compiled on the new distro.
but since the problem arose only with the new aic driver, i thought
it might be that you had a slightly different development
environment...?

anyway, robbert muller sent me the following simple workaround:


<quote>
Just create a shell script called yacc with the following content
-------------------
#!/bin/sh
bison --yacc $*
-------------------
i ran into the same problem with a school proiject here yesterday
</quote>


regards,

jörn


-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://www.folkwang-hochschule.de/~nettings/

  parent reply	other threads:[~2001-03-07 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 11:48 yacc dependency of aic7xxx driver Jörn Nettingsmeier
2001-03-07 14:06 ` Justin T. Gibbs
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 [this message]
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=3AA6576D.81501D0@folkwang-hochschule.de \
    --to=nettings@folkwang-hochschule.de \
    --cc=gibbs@scsiguy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox