Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <cagney@gnu.org>,
	gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
	newlib@sources.redhat.com
Subject: Re: [patch/rfc] Use i686-pc-linux-gnu as the releng target
Date: Mon, 12 Jan 2004 19:34:00 -0000	[thread overview]
Message-ID: <4002F6A8.6000807@redhat.com> (raw)
In-Reply-To: <20040112180911.GA20994@nevyn.them.org>



Daniel Jacobowitz wrote:
> On Mon, Jan 12, 2004 at 11:01:33AM -0500, Andrew Cagney wrote:
> 
>>Hello,
>>
>>GDB, and I suspect binutils, and just possibly newlib (true?), as part 
>>of the release process does:
>>	./configure sun4
>>(it is so that the .info et.al. files can be generated).  The problem is 
>>that GDB no longer configures for the good old sun4.
>>
>>This patch changes the system being used from "sun4" to "i686-pc-linux-gnu".
>>
>>For binutils, can the release engineer give this a wirl.
> 
> 
> Works fine.
> 
> 
>>For newlib, is this logic still used?  Can that part of the file be removed?
>>

We don't use it for generating our snapshot releases.  If you are building 
newlib on a native system, you have to specify --with-newlib in the 
configuration, otherwise, it normally doesn't get built.


>>Once we've sorted things here I'll see about pushing this upstream into 
>>GCC repository (gcc doesn't use this file).
> 
> 
> The GCC repository doesn't contain it, either.
> 


  reply	other threads:[~2004-01-12 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12 16:01 Andrew Cagney
2004-01-12 18:09 ` Daniel Jacobowitz
2004-01-12 19:34   ` J. Johnston [this message]
2004-01-15 23:23 ` Andrew Cagney

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=4002F6A8.6000807@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=cagney@gnu.org \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=newlib@sources.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