From: Paul Schlie <schlie@comcast.net>
To: <binutils@sources.redhat.com>, <gdb-patches@sources.redhat.com>
Cc: <insight@sources.redhat.com>, Keith Seitz <keiths@redhat.com>
Subject: [Patch] updated configure.in required to enable insight to build on OSX
Date: Tue, 22 Feb 2005 00:29:00 -0000 [thread overview]
Message-ID: <BE3FE701.92BD%schlie@comcast.net> (raw)
In-Reply-To: <1109021730.5123.2.camel@lindt.uglyboxes.com>
Might the following patch please be considered for inclusion into CVS
as soon as possible to enable Insight to build for OSX, Thank you:
--- old/src/configure.in Fri Jan 28 23:24:22 2005
+++ new/src/configure.in Sun Feb 20 14:49:03 2005
@@ -309,7 +309,7 @@ case "${host}" in
noconfigdirs="$noconfigdirs tk itcl libgui gdb dejagnu readline"
;;
*-*-darwin*)
- noconfigdirs="$noconfigdirs tk itcl libgui"
+ noconfigdirs="$noconfigdirs"
;;
esac
(and seems to execute correctly when invoked within the X11 terminal shell)
Thanks, -paul-
> From: Keith Seitz <keiths@redhat.com>
> Date: Mon, 21 Feb 2005 13:35:29 -0800
> To: Paul Schlie <schlie@comcast.net>
> Cc: <insight@sources.redhat.com>
> Subject: Re: Updated configure.in required to enable insight to build on OSX
>
> Hey, if it works, I don't have a problem. However, according to
> src/MAINTAINERS:
>
> Makefile.*; configure; configure.in; src-release
> Please notify the following of any committed patches.
> binutils@sources.redhat.com
> gdb-patches@sources.redhat.com
>
> So you would need to send a patch to the binutils and gdb-patches mailing
> lists.
>
> Keith
>
next prev parent reply other threads:[~2005-02-22 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 3:35 Updated " Paul Schlie
2005-02-21 21:35 ` Keith Seitz
2005-02-22 0:29 ` Paul Schlie [this message]
2005-02-22 9:18 ` [Patch] updated " Nick Clifton
2005-02-22 9:23 ` Paul Schlie
2005-02-22 9:35 ` Paul Schlie
2005-02-22 16:13 ` Andrew Cagney
2005-02-22 16:44 ` Paul Schlie
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=BE3FE701.92BD%schlie@comcast.net \
--to=schlie@comcast.net \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=keiths@redhat.com \
/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).