public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: suleman <sulemankm@gmail.com>
To: sid@sourceware.org
Subject: [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm 	component]
Date: Mon, 20 Aug 2007 10:56:00 -0000	[thread overview]
Message-ID: <1187607335.8053.0.camel@skmhome> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Forwarded message - Re: Sid verbose trace reveals missing sid-control-tksm component --]
[-- Type: message/rfc822, Size: 2400 bytes --]

From: suleman <sulemankm@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Sid verbose trace reveals missing sid-control-tksm component
Date: Mon, 20 Aug 2007 06:51:53 +0800
Message-ID: <1187563900.5733.3.camel@skmhome>

> strace sid  -e 'load libtclapi.la tcl_bridge_library' \
>             -e 'new sid-control-tksm tk' 2>&1 | grep tksm
> 

Here is the output of running this command on my system.

execve("/opt/sid/bin/sid", ["sid", "-e", "load libtclapi.la
tcl_bridge_lib"..., "-e", "new sid-control-tksm tk"], [/* 32 vars */]) =
0
write(2, "component type sid-control-tksm "..., 39component type
sid-control-tksm unknown) = 39

A more detailed output is as below; maybe it gives some useful hint?

open("/opt/sid/share/sidcomp", O_RDONLY|O_NONBLOCK|O_LARGEFILE|
O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=2096, ...}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
getdents64(3, /* 56 entries */, 4096)   = 2312
getdents64(3, /* 0 entries */, 4096)    = 0
close(3)                                = 0
open("/opt/sid/share", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=200, ...}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
getdents64(3, /* 8 entries */, 4096)    = 232
getdents64(3, /* 0 entries */, 4096)    = 0
close(3)                                = 0
open("/opt/sid/../share/sidcomp", O_RDONLY|O_NONBLOCK|O_LARGEFILE|
O_DIRECTORY) = -1 ENOENT (No such file or directory)
open("/opt/sid/../share", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) =
-1 ENOENT (No such file or directory)
write(2, "<literal>", 9<literal>)                = 9
write(2, ":", 1:)                        = 1
write(2, "1", 11)                        = 1
write(2, ": ", 2: )                       = 2
write(2, "component type sid-control-tksm "..., 39component type
sid-control-tksm unknown) = 39
write(2, "\n", 1
)                       = 1
write(2, "Configuration error.  Aborting.", 31Configuration error.
Aborting.) = 31
write(2, "\n", 1
)                       = 1
exit_group(3)                           = ?
Process 6117 detached


Bye,

Suleman

             reply	other threads:[~2007-08-20 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 10:56 suleman [this message]
2007-08-20 11:16 ` Frank Ch. Eigler
2007-08-25 23:36   ` suleman

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=1187607335.8053.0.camel@skmhome \
    --to=sulemankm@gmail.com \
    --cc=sid@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).