Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: Sam Steingold <sds@gnu.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] vacuous findlib warnings
Date: Mon, 26 Feb 2007 22:33:43 +0000	[thread overview]
Message-ID: <20070226223342.GA25086@furbychan.cocan.org> (raw)
In-Reply-To: <45E2FFF2.7060903@gnu.org>

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.

Rich.

-- 
Richard Jones
Red Hat UK Limited


  reply	other threads:[~2007-02-26 22:33 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 ` Richard Jones [this message]
2007-02-26 22:50   ` Sam Steingold

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=20070226223342.GA25086@furbychan.cocan.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=sds@gnu.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