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: Tue, 10 Mar 2015 18:48:00 -0000 [thread overview]
Message-ID: <54FF3C75.3000606@redhat.com> (raw)
In-Reply-To: <54FF34A6.9050100@daruma.com.br>
On 03/10/2015 11:15 AM, Marco Aurélio da Cruz wrote:
> The errors for 64-bits are bellow.
>
> checking for Tcl configuration... configure: WARNING: Can't find Tcl
> configuration definitions
> checking for existence of # no Tcl configs found/tclConfig.sh... could
> not find # no Tcl configs found/tclConfig.sh
> checking for Tk configuration... found /usr/lib64/tkConfig.sh
> checking for existence of /usr/lib64/tkConfig.sh... loading
> checking for Tcl private headers... configure: error: could not find
> private Tcl headers
> make[2]: *** [configure-libgui] Error 1
> make[2]: Leaving directory `/opt/arm-none-eabi/insight/bundle'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/opt/arm-none-eabi/insight/bundle'
> make: *** [notarget] Error 2
Patrick committed a patch which should have made this work. I build on
F21 all the time nowadays (directly from Patrick's git repo).
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.
Keith
next prev parent reply other threads:[~2015-03-10 18:48 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 [this message]
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
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=54FF3C75.3000606@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).