From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: matt@gushee.net
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] DBM in OCaml 3.07
Date: Wed, 15 Oct 2003 10:39:29 +0900 [thread overview]
Message-ID: <20031015103929E.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <20031015012445.GD26799@swordfish>
From: Matt Gushee <matt@gushee.net>
> > There seems to be another problem with gdbm-ndbm.h being ignored if
> > there is no gdbm_compat library, which might have to be fixed, but I'm
> > no gdbm exert. gdbm-ndbm.h was not checked on ocaml 3.06, but it has
> > lower priority than ndbm.h anyway.
>
> Ah, but it effectively has a *higher* priority in the configure script:
>
> for dir in /usr/include /usr/include/db1 /usr/include/gdbm; do
> if test -f $dir/ndbm.h; then
> ....
break
> fi
> if test -f $dir/gdbm-ndbm.h; then
> ....
break
> fi
> done
The break is supposed to get out of the loop, so if ndbm.h is in the
same directory, or a previous directory, it has priority.
This is a bit confusing, as if ndbm.h is in /usr/include/db1 and
gdbm-ndbm.h is in /usr/include, then gdbm-ndbm.h will be selected.
Is it your case?
> And maybe it would be useful to add a -dbm-includes option to the
> configure script, to help people work around this sort of situation. I
> suspect I'm not the only person with more than one DBM library.
Probably a good idea indeed.
Jacques
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-10-15 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 0:13 Matt Gushee
2003-10-15 0:40 ` Jacques Garrigue
2003-10-15 1:24 ` Matt Gushee
2003-10-15 1:39 ` Jacques Garrigue [this message]
2003-10-15 2:24 ` Matt Gushee
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=20031015103929E.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=caml-list@pauillac.inria.fr \
--cc=matt@gushee.net \
/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;
as well as URLs for NNTP newsgroup(s).