From: David Weinehall <tao@acc.umu.se>
To: Anuradha Ratnaweera <anuradha@gnu.org>
Cc: Lorenzo Marcantonio <lorenzo.marcantonio@sinfopragma.it>,
"H. Peter Anvin" <hpa@transmeta.com>,
root@chaos.analogic.com, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.4 failure to compile
Date: Sat, 19 May 2001 14:16:27 +0200 [thread overview]
Message-ID: <20010519141626.C6110@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.WNT.4.31.0105180827380.65-100000@pc209.sinfopragma.it> <Pine.LNX.4.21.0105181638000.251-100000@presario>
In-Reply-To: <Pine.LNX.4.21.0105181638000.251-100000@presario>; from anuradha@gnu.org on Fri, May 18, 2001 at 04:41:16PM +0600
On Fri, May 18, 2001 at 04:41:16PM +0600, Anuradha Ratnaweera wrote:
>
> On Fri, 18 May 2001, Lorenzo Marcantonio wrote:
>
> > On Thu, 17 May 2001, H. Peter Anvin wrote:
> >
> > > I think the header file you're talking about is the db1 header file,
> > > which has nothing to do with yacc -- it's the Berkeley libdb version 1,
> > > which is a pretty bad thing to require.
> > >
> >
> > I've got it to compile (and apparently work) even con libdb3... which
> > has the compability header db_185.h (or something similar).
> >
> > IIRC, libdb1 was bundled with libc till release 2.1.3. Since 2.2 they've
> > said 'get it at sleepycat...'.
> >
> > BTW, there are ifdef inside the driver about which header to include
> > (db.h or db_185.h IIRC).
> >
> > I still doesn't comprend what does it NEED FOR the libdb...
>
> I don't do any module programming yet, but the lkmpg lists "Using standard
> libraries" under "Common Pitfalls". Is anything unusual going on here?
Yup. The code in question is not a module, but rather a userspace-program
that generates microcode for the SCSI-adapter(s) in question. As such,
using standard libraries is fully ok. The debate is whether libdb1
is to be considered common enough.
Regards: David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-05-19 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 17:23 Richard B. Johnson
2001-05-17 17:38 ` Tim Hockin
2001-05-17 18:03 ` Christoph Hellwig
2001-05-17 18:32 ` H. Peter Anvin
2001-05-17 18:47 ` Richard B. Johnson
2001-05-17 18:52 ` H. Peter Anvin
2001-05-18 6:32 ` Lorenzo Marcantonio
2001-05-18 10:41 ` Anuradha Ratnaweera
2001-05-19 12:16 ` David Weinehall [this message]
2001-05-17 18:33 Cress, Andrew R
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=20010519141626.C6110@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=anuradha@gnu.org \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.marcantonio@sinfopragma.it \
--cc=root@chaos.analogic.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®