From: "Frank Ch. Eigler" <fche@redhat.com>
To: suleman <sulemankm@gmail.com>
Cc: sid@sourceware.org
Subject: Re: Sid verbose trace reveals missing sid-control-tksm component
Date: Sat, 18 Aug 2007 12:32:00 -0000 [thread overview]
Message-ID: <20070818123227.GH5536@redhat.com> (raw)
In-Reply-To: <1187426565.20560.7.camel@skmhome>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
Hi -
On Sat, Aug 18, 2007 at 04:42:45PM +0800, suleman wrote:
> Running the sid-arm-elf [...] with --verbose reveals that the
> sid-control-tksm component is missing from the libtclapi library.
> [...]
sid-control-tksm is not exactly "within" the library, but loaded by it
in script form from $prefix/share/sidcomp. You'll see the
sid-control-tksm.tk file right in there.
strace sid -e 'load libtclapi.la tcl_bridge_library' \
-e 'new sid-control-tksm tk' 2>&1 | grep tksm
This may give a hint.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-08-18 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 8:43 suleman
2007-08-18 12:32 ` Frank Ch. Eigler [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=20070818123227.GH5536@redhat.com \
--to=fche@redhat.com \
--cc=sid@sourceware.org \
--cc=sulemankm@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).