From: Christoph Hellwig <hch@caldera.de>
To: gibbs@scsiguy.com ("Justin T. Gibbs")
Cc: linux-kernel@vger.kernel.org
Subject: Re: yacc dependency of aic7xxx driver
Date: Wed, 7 Mar 2001 15:42:19 +0100 [thread overview]
Message-ID: <200103071442.PAA14348@ns.caldera.de> (raw)
In-Reply-To: <200103071406.f27E6pO25638@aslan.scsiguy.com>
In article <200103071406.f27E6pO25638@aslan.scsiguy.com> you wrote:
> 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.
Yepp, gmake is kindof stupid in that respect - it does also not try
to use flex if there is no lex, etc... I'd really vote for a BSDish
sys.mk.
> 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.
What about simply removing the firmware source and assembler from the
kernel tree? We have lots of firmware in the kernel tree for which
there isn't even firmware avaible...
The few people that want to do firware development could download it
from your ftp site.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-03-07 14:43 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 [this message]
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=200103071442.PAA14348@ns.caldera.de \
--to=hch@caldera.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 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.