This is the mail archive of the
insight-prs@sourceware.org
mailing list for the Insight project.
Re: insight/304: library problem with another software
- From: kseitz at sources dot redhat dot com
- To: insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, qijungu at gmail dot com
- Date: 30 Nov 2006 22:50:14 -0000
- Subject: Re: insight/304: library problem with another software
- Reply-to: kseitz at sources dot redhat dot com, insight-prs at sources dot redhat dot com, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, qijungu at gmail dot com, insight-gnats at sources dot redhat dot com
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
Responsible-Changed-Why:
mine
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Thu Nov 30 22:50:14 2006
State-Changed-Why:
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.
http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=304