From: suleman <sulemankm@gmail.com>
To: sid@sourceware.org
Subject: [Fwd: Re: [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm component]]
Date: Mon, 20 Aug 2007 11:33:00 -0000 [thread overview]
Message-ID: <1187609507.8053.12.camel@skmhome> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Forwarded message - Re: [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm component] --]
[-- Type: message/rfc822, Size: 1754 bytes --]
From: suleman <sulemankm@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: [Fwd: Re: Sid verbose trace reveals missing sid-control-tksm component]
Date: Mon, 20 Aug 2007 19:31:27 +0800
Message-ID: <1187609475.8053.10.camel@skmhome>
On Mon, 2007-08-20 at 07:16 -0400, Frank Ch. Eigler wrote:
> 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.
I tried to use two configure commands (none of them worked) i.e.
/src/sid/src/configure --prefix=/opt/sid 2>&1 | tee configure.out
/src/sid/src/configure --prefix=/opt/sid --exec-prefix=/opt/sid 2>&1 |
tee configure.out
The folder /opt/sid/share/sidcomp has been correctly created by build
install and the sid-control-tksm.tk etc is present there.
Actually, as the strace output is showing, the code isn't trying to find
the folder /opt/sid/share/sidcomp, it is looking for a folder
called /opt/sid/../share/sidcomp. Isn't it strange (I mean the '..' in
the path)?
Suleman
reply other threads:[~2007-08-20 11:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1187609507.8053.12.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).