Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: msnyder@redhat.com
Cc: Scott Bambrough <scottb@netwinder.org>,
	GDB Patches Mail List <gdb-patches@sourceware.cygnus.com>
Subject: Re: RFC: changes to configure.in and configure
Date: Tue, 07 Nov 2000 20:07:00 -0000	[thread overview]
Message-ID: <3A08D009.4D0AEAB8@cygnus.com> (raw)
In-Reply-To: <3986E6A3.6B3C@redhat.com>

Michael Snyder wrote:
> 
> Scott Bambrough wrote:
> >
> > Andrew Cagney wrote:
> > >
> > > I'm not sure how this patch:
> > >
> > > -# else
> > > +else
> > >  # GDBserver is only useful in a "native" enviroment
> > > -# configdirs=`echo $configdirs | sed 's/gdbserver//'`
> > > +configdirs=`echo $configdirs | sed 's/gdbserver//'`
> > >  fi
> > >  changequote([,])
> >
> > This bit of the patch removes gdbserver from $configdirs unless it is a native
> > build.
> 
> Why?  What about host-x-host?  What about embedded linux?

I think, the process of building cross comiling gdbserver should be kept
separate to the normal config/build of GDB.  Instead either:

	o	a separatly tree configured
		for a canadian cross build
		(use cross compiler to
		cross compile gdbserver)
		
	o	something very similar to newlib
		(newlib is built using the
		uninstalled cross compiler from
		the build tree)

	enjoy,
		Andrew


      parent reply	other threads:[~2000-11-07 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3985A85C.C246C623@netwinder.org>
     [not found] ` <20000731124035.N9027@cygnus.com>
2000-07-31  9:58   ` Scott Bambrough
     [not found] ` <39863CD3.A527CEC3@cygnus.com>
2000-08-01  7:38   ` Scott Bambrough
     [not found]     ` <3986E6A3.6B3C@redhat.com>
2000-11-07 20:07       ` Andrew Cagney [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=3A08D009.4D0AEAB8@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=msnyder@redhat.com \
    --cc=scottb@netwinder.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