From: Roland Schwingel <roland@onevision.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>,
insight@sourceware.org, Keith Seitz <keiths@redhat.com>
Subject: RE: [PATCH] Add missing prototype in gdbtk.c
Date: Fri, 30 Mar 2012 13:48:00 -0000 [thread overview]
Message-ID: <4F75B980.5070109@onevision.com> (raw)
Hi Pierre...
insight-owner@sourceware.org wrote on 30.03.2012 15:31:24:
>
> I wasn't sure about the fact that this is a real
> Prototype requirement or not, so I wanted to ask anyway...
>
> Patch committed.
>
> Roland, could you please confirm that
> this also works for mingw64.
You have been faster than me on this...
Yes it works here, too - as already replied in my other post.
>
> By the way, I got a working insight for mingw32,
> which I was unable to get for a lllloooonnngggg time!
> A really big thank to Roland for this!
You are welcome. I am also happy to have both a 32bit and 64bit insight!
It was worth the effort.
> PS: I treid to compiled a mingw64 version of insight,
> but I get failures here:
There is IMHO no way to get insight running on 64bit windows using the
current intree tcl/tk 8.4. I am using tcl/tk 8.6 for this. I am not done
with sending all my patches for building a 64bit windows insight. There
is still some way to go!
See my description here
http://sourceware.org/ml/insight/2012-q1/msg00050.html
and here
http://sourceware.org/ml/insight/2012-q1/msg00017.html
If you like to I can supply you a 64bit binary (but have to check
whether I have enabled pascal in my gdb sources ;-)
Roland
next reply other threads:[~2012-03-30 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:48 Roland Schwingel [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-30 13:36 Roland Schwingel
2012-03-19 12:10 Roland Schwingel
2012-03-29 23:02 ` Keith Seitz
2012-03-30 13:03 ` Pierre Muller
2012-03-30 13:10 ` Keith Seitz
2012-03-30 13:32 ` Pierre Muller
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=4F75B980.5070109@onevision.com \
--to=roland@onevision.com \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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).