From: "Marco Aurélio da Cruz" <m.cruz@daruma.com.br>
To: insight@sourceware.org
Subject: Re: Status of insight/gdbtk
Date: Fri, 20 Mar 2015 14:45:00 -0000 [thread overview]
Message-ID: <55083FDA.9090006@daruma.com.br> (raw)
In-Reply-To: <550082EC.1050508@redhat.com>
Hi there.
On 03/11/2015 03:01 PM, Keith Seitz wrote:
>
> Does /usr/lib64/tclConfig.sh exist? [This is where the file lives on my
> Fedora 21 box, which I don't think is any different from Fedora 20.]
> When configure complains that "WARNING: Can't find Tcl configuration
> definitions," this means that it is unable to locate this file.
>
> where prefix is given by the configure option "--prefix" and usrlibdir
> is computed by configure. ["/usr/lib" on 32-bit architectures,
> "/usr/lib32" with "-m32" on 64-bit architectures, and "/usr/lib64" on
> 64-bit architectures]
>
> tclConfig.sh is supplied by the tcl-devel package on Fedora.
>
>
Yes, you were right. It was my fault. It was missing tcl-devel.
Everething compiled OK on 64-bit now. Thank you again.
Now, I noticed a kind of screen bug when running Insight. I put an
image here: http://goo.gl/Hgli5V
It is related to use of some characters in ISO8859-1. If I save
my source in UTF-8, Insight shows it correctly.
Regards,
Marco
prev parent reply other threads:[~2015-03-17 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 21:29 Mikhail T.
2014-12-02 13:16 ` Patrick Monnerat
2015-03-09 17:37 ` Marco Aurélio da Cruz
2015-03-10 13:26 ` Patrick Monnerat
2015-03-10 18:15 ` Marco Aurélio da Cruz
2015-03-10 18:48 ` Keith Seitz
2015-03-11 10:42 ` Patrick Monnerat
2015-03-11 14:12 ` Marco Aurélio da Cruz
2015-03-11 17:45 ` Patrick Monnerat
2015-03-11 18:01 ` Keith Seitz
2015-03-20 14:45 ` Marco Aurélio da Cruz [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=55083FDA.9090006@daruma.com.br \
--to=m.cruz@daruma.com.br \
--cc=insight@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).