From: Paul Schlie <schlie@comcast.net>
To: Nick Clifton <nickc@redhat.com>
Cc: <binutils@sources.redhat.com>, <gdb-patches@sources.redhat.com>,
<insight@sources.redhat.com>, Keith Seitz <keiths@redhat.com>
Subject: Re: [Patch] updated configure.in required to enable insight to build on OSX
Date: Tue, 22 Feb 2005 09:35:00 -0000 [thread overview]
Message-ID: <BE4066DE.92E1%schlie@comcast.net> (raw)
In-Reply-To: <BE406439.92DE%schlie@comcast.net>
Actually come to think of it, might there be any quick convenient way
to disable sim, sid, rda, and libgloss from trying to build without
being explicitly enabled (or even prevented if explicitly disabled)?
As I've had to basically manually re-name or remove those directories,
to prevent them from building when not desired?
> From: Paul Schlie <schlie@comcast.net>
>
> Understood, Thank you, -paul-
>
>
>> From: Nick Clifton <nickc@redhat.com>
>>
>> Hi Paul,
>>
>>> *-*-darwin*)
>>> - noconfigdirs="$noconfigdirs tk itcl libgui"
>>> + noconfigdirs="$noconfigdirs"
>>
>> There is no point in just copying noconfigdirs onto itself so I have
>> checked in a variation of your patch with the entry for *-*-darwin*
>> entirely removed.
>>
>> Cheers
>> Nick
>>
>> <toplevel>/ChangeLog
>> 2005-02-22 Paul Schlie <schlie@comcast.net>
>>
>> * configure.in: Allow darwin targeted ports to build tk, itcl and
>> libgui.
>
next prev parent reply other threads:[~2005-02-22 9:35 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 ` [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 [this message]
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=BE4066DE.92E1%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 \
--cc=nickc@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).