Re: [Patch] updated configure.in required to enable insight to build on OSX

[Paul Schlie <schlie@comcast.net>]

Actually yes, typically simply co -d src ... and grab everything,
then typically merge gcc into it (which I know isn't blessed, but
have generally found it more reliable for the things that should
likely be in common, to literally be in common; so would be nice
to have a top-level configure maintained, it would seem, as I don't
think I'm the only one?

[personally seems a little archaic for gcc to still remain disassociated
 from the src cvs tree, and end up having to manually check into both?]


> From: Andrew Cagney <cagney@gnu.org>
> Date: Tue, 22 Feb 2005 11:09:59 -0500
> To: Paul Schlie <schlie@comcast.net>
> Cc: Nick Clifton <nickc@redhat.com>, <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
> 
> Paul Schlie wrote:
>> 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?
> 
> Did you use "cvs update -d" in the top level directory?  Neither the
> BINUTILS, nor GDB modules check any of those directories out.
> 
> Andrew