Message-Id: <200103070010.f270ApO14502@aslan.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 
In-Reply-To: Your message of "Tue, 06 Mar 2001 15:43:22 PST."
             <000f01c0a697$3b1924f0$0200a8c0@theoesters.com> 
Date: Tue, 06 Mar 2001 17:10:51 -0700
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
Sender: linux-kernel-owner@vger.kernel.org

>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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/