public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Marco Aurélio da Cruz" <m.cruz@daruma.com.br>
To: insight@sourceware.org
Subject: Re: Status of insight/gdbtk
Date: Wed, 11 Mar 2015 14:12:00 -0000	[thread overview]
Message-ID: <55004D46.60603@daruma.com.br> (raw)
In-Reply-To: <AB5E58B87EB73C46A38073D8F459F113DA00D7@dataspheresrv01>

Hi Patrick. Hi Keith.


On 03/10/2015 03:48 PM, Keith Seitz wrote:
>
> 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

The pach file was correctly applied to "bundle" folder before compiling.



On 03/11/2015 07:42 AM, Patrick Monnerat wrote:
>  
> Marco Aurélio da Cruz wrote:
>
>> So, I forgot to tell you before. I can't compile it on a Fedora 20 64-bit. I tried with CFLAGS=-m32 but have no success too.
> All Tcl/Tk/Tcl-devel/Tk-devel packgages are installed for x86_64 and .i686.
>
> Fedora 20 x86_64 is the environment on which I do all my work on insight and it works perfectly.
> As said Keith, I think your build tree is not clean and that caused the error you mention. Try to do the following things:
> - remove the "bundle" subdirectory.
> - git pull
> - redo the build as mentioned in the README file from the "autoconf" command.
>
> This should work.

Patrick, I did a clean instalation, twice. And I always removed the
"bundle" before compiling. And as I said above, all patches were
correctly applied.  I will try again later.


> Please note that insight is packaged for F20. This is an old version (~6 months) but it works. So if you need insight only for using it, you can just "yum install insight".
>

Right, but I need it for arm-none-eabi. The 32-bit version I compiled is
working like a charm in my 64-bit computer.


Thank you guys for your support.


Cheers

Marco




-- 
Marco Aurélio da Cruz | Eng. P&D Automação | tel.: 12-3609-5105
Urmet Daruma - Av. Independência, 3500 - Taubaté - SP - CEP 12032-000
www.daruma.com.br

  reply	other threads:[~2015-03-11 14:12 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 [this message]
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=55004D46.60603@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).