From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] hugin error message
Date: Sun, 16 Mar 2008 11:15:22 +0200 [thread overview]
Message-ID: <200803161115.22493.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <47DC35A6.6050401@gmail.com>
On Saturday 15 March 2008, David Harel wrote:
> Don't you think the error message should have been more specific
> about which library causes the conflict? Is it hugin error message?
Yes, the message is not very illuminating. You'd think the app that
emitted it would mention where it comes from and which libs it was
referring it <sigh>
The revdep-rebuild and ldd output also doesn't say much other than mono
is involved, which I don't know a whole lot about. My next tactic would
be to run hugin under strace, and see which library calls came just
before the error. This however can be a long and tedious process.
Hopefully someone else more familiar with mono will come along soon
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-03-16 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 20:28 [gentoo-user] hugin error message David Harel
2008-03-13 22:38 ` Alan McKinnon
2008-03-15 20:46 ` David Harel
2008-03-16 9:15 ` Alan McKinnon [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=200803161115.22493.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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