From: Anonymous <nobody@slug.slugish.net>
To: insight@sourceware.org
Subject: Re: [PATCH] Fix build gdbtk-hooks.c problem [was Re: grossly out of date???]
Date: Wed, 24 Oct 2012 17:24:00 -0000 [thread overview]
Message-ID: <ef54ae7ae30f2c5bf26945f02b4145b1@slug.slugish.net> (raw)
In-Reply-To: <50880A78.4080200@redhat.com>
> Here is a patch which fixes the build problem. This is the only problem
> that I noticed. If there are others, please send a note to the list to
> draw my attention to it.
Thanks for that, I'll try it as soon as I can.
> I do try to keep insight building/working.
I've had bad luck over the past two years with several builds and when it
does build I've had some extremely annoying breakage in assembly language
on Intel x86_64. In 32 bit mode it works great. It will be excellent when
the x86_64 problems are sorted. Thanks for the help.
Rob
prev parent reply other threads:[~2012-10-24 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 6:40 grossly out of date??? Roland Schwingel
2012-10-24 10:59 ` Dave U. Random
2012-10-24 15:34 ` [PATCH] Fix build gdbtk-hooks.c problem [was Re: grossly out of date???] Keith Seitz
2012-10-24 17:24 ` Anonymous [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=ef54ae7ae30f2c5bf26945f02b4145b1@slug.slugish.net \
--to=nobody@slug.slugish.net \
--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).