All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Cavan <johnc@damncats.org>
To: Phil Oester <kernel@theoesters.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error compiling aic7xxx driver on 2.4.2-ac13
Date: Tue, 06 Mar 2001 19:13:30 -0500	[thread overview]
Message-ID: <3AA57D2A.34223B4E@damncats.org> (raw)
In-Reply-To: <000f01c0a697$3b1924f0$0200a8c0@theoesters.com>

Phil Oester wrote:
> 
> one more try...
> 
> anyone else get the following:
> 
> 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'

The location of db_185.h is somewhat vendor dependent. In my case
(Mandrake cooker), the location is in /usr/include/db3 rather than
/usr/include/db. You have a couple of choices for now... symlink db3 to
db if that is your situation or back out that portion of the patch to
use the original db1 library. I personally chose the symlink, but it
does highlight the problem of having userspace dependencies in the
tree...

John

  parent reply	other threads:[~2001-03-07  0:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 23:43 Error compiling aic7xxx driver on 2.4.2-ac13 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
2001-03-07  0:13 ` John Cavan [this message]
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=3AA57D2A.34223B4E@damncats.org \
    --to=johnc@damncats.org \
    --cc=kernel@theoesters.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.