From: Keith Seitz <keiths@redhat.com>
To: Paul Schlie <schlie@comcast.net>
Cc: insight@sources.redhat.com
Subject: Re: Updated configure.in required to enable insight to build on OSX
Date: Mon, 21 Feb 2005 21:35:00 -0000 [thread overview]
Message-ID: <1109021730.5123.2.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <BE3EC11C.9289%schlie@comcast.net>
On Sun, 2005-02-20 at 22:35 -0500, Paul Schlie wrote:
> ;;
> *-*-darwin*)
> - noconfigdirs="$noconfigdirs tk itcl libgui"
> + noconfigdirs="$noconfigdirs"
>
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-21 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 3:35 Paul Schlie
2005-02-21 21:35 ` Keith Seitz [this message]
2005-02-22 0:29 ` [Patch] updated " Paul Schlie
2005-02-22 9:18 ` 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=1109021730.5123.2.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=schlie@comcast.net \
/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).