From: Keith Seitz <keiths@redhat.com>
To: "Marco Aurélio da Cruz" <m.cruz@daruma.com.br>, insight@sourceware.org
Subject: Re: Status of insight/gdbtk
Date: Wed, 11 Mar 2015 18:01:00 -0000 [thread overview]
Message-ID: <550082EC.1050508@redhat.com> (raw)
In-Reply-To: <55004D46.60603@daruma.com.br>
On 03/11/2015 07:12 AM, Marco Aurélio da Cruz wrote:
> On 03/10/2015 03:48 PM, Keith Seitz wrote:
>> Does your repository have patches/binutils-gdb/003-tclconfig.patch? If
>> so, make sure that all the files were regenerated properly. You can
>> search for "usrlibdir" in gdb/configure to check. If it isn't in
>> there, your configure files were not regenerated to include the fix.
>
> The pach file was correctly applied to "bundle" folder before compiling.
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.
The patch I referred to earlier changes configure to look in the
following directories:
${prefix}/lib, /usr/local/lib, /usr/contrib/lib, /usr/lib,
${usrlibdir}, ${usrlibdir}/tcl[[8-9]].[[0-9]], and
${usrlibdir}/tcl[[8-9]].[[0-9]]*
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.
Keith
next prev parent reply other threads:[~2015-03-11 18:01 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 [this message]
2015-03-20 14:45 ` Marco Aurélio da Cruz
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=550082EC.1050508@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=m.cruz@daruma.com.br \
/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).