From: fche@redhat.com (Frank Ch. Eigler)
To: David Gaydou <dgaydou@gmail.com>
Cc: sid@sources.redhat.com
Subject: Re: Sid verbose trace reveals missing sid-control-tksm component - again
Date: Thu, 26 Feb 2009 20:12:00 -0000 [thread overview]
Message-ID: <y0mprh5nek5.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <58f42aa00902261057s47ddddabg909c6307e51aa2a1@mail.gmail.com> (David Gaydou's message of "Thu, 26 Feb 2009 16:57:53 -0200")
David Gaydou <dgaydou@gmail.com> writes:
> [...] and may be, this help...
>
> david@ciii-p227:~/src/sid/component/tcl$ ./configure | grep tcl
> checking tcl in build tree... -L../../../tcl/unix -ltcl8.4
> checking tcl.h usability... no
> checking tcl.h presence... no
> checking for tcl.h... no
The config.log file should explain more about this problem.
Another possibility is to remove the tcl & tk subdirectories
from the sid tree (by renaming temporarily) to see if the
system tcl libraries are deemed suitable.
- FChE
next prev parent reply other threads:[~2009-02-26 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 16:30 David Gaydou
2009-02-26 18:22 ` Frank Ch. Eigler
2009-02-26 18:58 ` David Gaydou
2009-02-26 20:12 ` Frank Ch. Eigler [this message]
2009-02-27 13:59 ` David Gaydou
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=y0mprh5nek5.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=dgaydou@gmail.com \
--cc=sid@sources.redhat.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).