public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
* [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm  component]
@ 2007-08-20 10:56 suleman
  2007-08-20 11:16 ` Frank Ch. Eigler
  0 siblings, 1 reply; 3+ messages in thread
From: suleman @ 2007-08-20 10:56 UTC (permalink / raw)
  To: sid

[-- 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm  component]
  2007-08-20 10:56 [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm component] suleman
@ 2007-08-20 11:16 ` Frank Ch. Eigler
  2007-08-25 23:36   ` suleman
  0 siblings, 1 reply; 3+ messages in thread
From: Frank Ch. Eigler @ 2007-08-20 11:16 UTC (permalink / raw)
  To: suleman; +Cc: sid

Hi -

> [...]
> 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) = -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)
> [...]

Yes, well, both of these directories should exist.  Something must
be strange about the way you configured the build tree, or perhaps
the "make install" in the tcl directory did not complete for some
reason.

- FChE

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm  component]
  2007-08-20 11:16 ` Frank Ch. Eigler
@ 2007-08-25 23:36   ` suleman
  0 siblings, 0 replies; 3+ messages in thread
From: suleman @ 2007-08-25 23:36 UTC (permalink / raw)
  To: sid

Well, I've found and fixed the problem.

The problem is that when I run configure script from the topmost source
folder, and then run 'make all', the tk.h header is not detected  and
the config.h file created in the sid/component/tcl folder does not
define HAVE_TK_H for some reason and thus the tksm component is not
reported by the bridge-tcl-library.

If I manually run the configure script in the sid/component/tcl folder.
the tk.h header is correctly detected and config.h has the HAVE_TK_H
define set to 1.  If I now compile, tksm works Ok.

Bye,

Suleman

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-08-25 23:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-08-20 10:56 [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm component] suleman
2007-08-20 11:16 ` Frank Ch. Eigler
2007-08-25 23:36   ` suleman

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).