From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: leroyljr@ccsi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Failure to Compile AIC7xxx Driver
Date: Thu, 16 Aug 2001 19:04:12 -0600 [thread overview]
Message-ID: <200108170104.f7H14CI83159@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Thu, 16 Aug 2001 19:15:38 CDT." <200108170013.f7H0DoO21290@ccsi.com>
>If nobody has brought this up yet, I want to report this issue.
>
>Here is what happened when I tried to build the aic7xxx driver for 2.4.9:
>
>aicasm/aicasm_scan.l: In function `yylex':
>aicasm/aicasm_scan.l:115: `T_VERSION' undeclared (first use in this function)
>aicasm/aicasm_scan.l:115: (Each undeclared identifier is reported only once
>aicasm/aicasm_scan.l:115: for each function it appears in.)
>aicasm/aicasm_scan.l:132: `T_STRING' undeclared (first use in this function)
>
>This is for the new driver, BTW.
I tried to reproduce this locally, but was never able to do so. My
best guess is that the default rules for building lex/yacc grammers don't
include proper dependencies for the generated y.tab.h file. Of course,
it shouldn't be necessary. Both aicasm_gram.y and aicasm_scan.l should
have newer dates than the y.tab.h file from a previous build (both are
updated for 2.4.9) and aicasm_gram.c is listed first in the dependency
line, so yacc should have already been run prior to the compilation of
aicasm_scan.c.
Perhaps a make guru can lend some insight?
If you manually go into drivers/scsi/aic7xxx/aicasm and do a make clean, the
error should go away.
Of course, you could just disable the build of the firmware in your
kernel config...
--
Justin
next prev parent reply other threads:[~2001-08-17 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 0:15 leroyljr
2001-08-17 1:04 ` Justin T. Gibbs [this message]
2001-08-17 2:36 ` Pete Toscano
2001-08-21 2:21 ` Keith Owens
2001-08-21 2:53 ` Justin T. Gibbs
2001-08-17 17:31 ` thobi
2001-08-17 17:39 ` Justin T. Gibbs
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=200108170104.f7H14CI83159@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=leroyljr@ccsi.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
all inboxes | Powered by JetHome®