From: Sam Steingold <sds@gnu.org>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: vacuous findlib warnings
Date: Mon, 26 Feb 2007 17:50:54 -0500 [thread overview]
Message-ID: <45E3644E.60806@gnu.org> (raw)
In-Reply-To: <20070226223342.GA25086@furbychan.cocan.org>
Richard Jones wrote:
> On Mon, Feb 26, 2007 at 10:42:42AM -0500, Sam Steingold wrote:
>> I see findlib warnings like this:
>> findlib: [WARNING] Interface qbase.cmi occurs in several directories:
>> ../../lib, .
>> this is because there is indeed ../../lib/qbase.cmi which is a symbolic
>> link pointing to ./qbase.cmi (so there is no real duplication, the files
>> point to the same inode).
>>
>> Is it possible to modify findlib to check that the files are really
>> different disk objects (inodes) before issuing the warning?
>
> Agreed. Even better if it could compare the md5 of the interfaces.
"=" vs "=="? :-)
I would rather not use a checksum here - it has no advantage over an
honest cmp(1). Actually, cmp(1) is probably faster (because it does not
have to read the whole file to give a negative answer), and it returns
TRT (no false positives).
Sam.
prev parent reply other threads:[~2007-02-26 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 15:42 Sam Steingold
2007-02-26 22:33 ` [Caml-list] " Richard Jones
2007-02-26 22:50 ` Sam Steingold [this message]
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=45E3644E.60806@gnu.org \
--to=sds@gnu.org \
--cc=caml-list@inria.fr \
--cc=rich@annexia.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 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).