From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "Phil Oester" <kernel@theoesters.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Error compiling aic7xxx driver on 2.4.2-ac13
Date: Tue, 06 Mar 2001 17:10:51 -0700 [thread overview]
Message-ID: <200103070010.f270ApO14502@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Tue, 06 Mar 2001 15:43:22 PST." <000f01c0a697$3b1924f0$0200a8c0@theoesters.com>
>make[5]: Entering directory
>`/usr/src/linux-2.4.2-ac13/drivers/scsi/aic7xxx/aicasm'
>lex -t aicasm_scan.l > aicasm_scan.c
>gcc -I/usr/include -ldb aicasm_gram.c aicasm_scan.c aicasm.c
>aicasm_symbol.c -o aicasm
>aicasm_symbol.c:39: db/db_185.h: No such file or directory
>make[5]: *** [aicasm] Error 1
>make[5]: Leaving directory
>`/usr/src/linux-2.4.2-ac13/drivers/scsi/aic7xxx/aicasm'
Is it prudent to build the assembler from within the kernel
build? I'd personally love to ditch the aic7xxx_seq.h and
aic7xxx_reg.h files from the kernel distribution and I even
have the makefiles for version 6.1.6 of the driver. The only
question is, with so many distributions out there can we rely
on lex, yacc, and berkeley DB existing on the host system?
As to your *real* problem. My guess is that the dependency
to regenerate the files is getting hit. This often happens
during a patch upgrade where only one of the two generated files
is updated. If you touch aic7xxx_reg.h and aic7xxx_seq.h the
build will work fine. Alternatively, you can figure out how to
get Berekeley DB installed on your system.
--
Justin
next prev parent reply other threads:[~2001-03-07 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 23:43 Phil Oester
2001-03-07 0:04 ` J . A . Magallon
2001-03-07 0:51 ` Alan Cox
2001-03-07 4:09 ` Phil Oester
2001-03-07 14:51 ` J . A . Magallon
2001-03-07 0:10 ` Justin T. Gibbs [this message]
2001-03-07 0:13 ` John Cavan
2001-03-07 0:49 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-03-06 23:36 Phil Oester
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=200103070010.f270ApO14502@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®