public inbox for
help / color / mirror / Atom feed
Subject: Re: insight/304: library problem with another software
Date: Thu, 30 Nov 2006 22:50:00 -0000	[thread overview]
Message-ID: <> (raw)

Synopsis: library problem with another software

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Nov 30 22:50:14 2006
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Thu Nov 30 22:50:14 2006
    There are two different problems that I can think of. You're bug report is a little vague, so I'm going to have to guess at the real failure.
    First guess is that aMSN (sorry, don't know what that is) is using Tcl, Tk, or Itcl, and uses a different version that the one we ship with. So you're getting library conflicts. The easiest way to resolve this is to simply install insight in its own directory instead of a system directory. This is easily accomplished by using the "--prefix" option to configure.
    The other problem could be that aMSN is attempting to dynamically load a package. For arcane reasons, shared builds are disabled by default. In this case, simply pass the configure option "--enable-shared" and rebuild/install.
    If it is neither of these, I'm going to have have more information. How insight was configured, the exact error message reported when aMSN runs, and the like.

             reply	other threads:[~2006-11-30 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 22:50 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-03 17:13 qijungu

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).