public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rod Stewart <stewart@lab43.org>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: config.sub
Date: Tue, 03 Oct 2000 13:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0010031646280.18110-100000@dystopia.lab43.org> (raw)
In-Reply-To: <10010032059.AA01086@vlsi1.ultra.nyu.edu>

On Tue, 3 Oct 2000, Richard Kenner wrote:

> Could somebody remind me how changes to config.sub are handled?
> 
> The particular change I want to make is that it has "hppa64" while
> configure.in has the correct "hppa*64".

Please someone update it.  For my reason why see
http://gcc.gnu.org/ml/gcc-bugs/2000-09/msg00385.html .  It would be nice to
not have my builds show up as armv4l-unknown-unknown-linux-gnu.

My understanding from what has been said in the past is that any
maintainer can update them from the master copies at
  :pserver:anoncvs@subversions.gnu.org:/cvs co config

If you want functionality which is diffent, you need to submit it the
people who keep the master copies up to date.  There is a link off of
http://sources.redhat.com/autoconf page, I believe.

Here is the relavant patch from subversions.gnu.org.

-Rms

Index: config.sub
===================================================================
RCS file: /cvs/gcc/egcs/config.sub,v
retrieving revision 1.48
diff -u -p -r1.48 config.sub
--- config.sub	2000/09/05 10:33:51	1.48
+++ config.sub	2000/10/03 20:53:29
@@ -3,7 +3,7 @@
 #   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000
 #   Free Software Foundation, Inc.
 
-version='2000-09-05'
+version='2000-09-11'
 
 # This file is (in principle) common to ALL GNU software.
 # The presence of a machine in this file suggests that SOME GNU software
@@ -204,7 +204,7 @@ case $basic_machine in
 	# Recognize the basic CPU types without company name.
 	# Some are omitted here because they have special meanings below.
 	tahoe | i860 | ia64 | m32r | m68k | m68000 | m88k | ns32k | arc | arm \
-		| arme[lb] | armv* | pyramid | mn10200 | mn10300 | tron | a29k \
+		| arme[lb] | armv[2345] | armv[345][lb] | pyramid | mn10200 | mn10300 | tron | a29k \
 		| 580 | i960 | h8300 \
 		| x86 | ppcbe | mipsbe | mipsle | shbe | shle | armbe | armle \
 		| hppa | hppa1.0 | hppa1.1 | hppa2.0 | hppa2.0w | hppa2.0n \
@@ -1052,7 +1052,7 @@ case $os in
 	-ns2 )
 	        os=-nextstep2
 		;;
-	-nsk)
+	-nsk*)
 		os=-nsk
 		;;
 	# Preserve the version number of sinix5.
Index: config.guess
===================================================================
RCS file: /cvs/gcc/egcs/config.guess,v
retrieving revision 1.39
diff -u -p -r1.39 config.guess
--- config.guess	2000/09/05 10:33:51	1.39
+++ config.guess	2000/10/03 20:53:31
@@ -3,7 +3,7 @@
 #   Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000
 #   Free Software Foundation, Inc.
 
-version='2000-09-05'
+version='2000-10-03'
 
 # This file is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
@@ -698,8 +698,7 @@ EOF
 	# The BFD linker knows what the default object file format is, so
 	# first see if it will tell us. cd to the root directory to prevent
 	# problems with other programs or directories called `ld' in the path.
-	ld_help_string=`cd /; ld --help 2>&1`
-	ld_supported_emulations=`echo $ld_help_string \
+	ld_supported_emulations=`cd /; ld --help 2>&1 \
 			 | sed -ne '/supported emulations:/!d
 				    s/[ 	][ 	]*/ /g
 				    s/.*supported emulations: *//
@@ -866,8 +865,8 @@ EOF
 	  # GCC wants to distinguish between linux-gnuoldld and linux-gnuaout.
 	  # If ld does not provide *any* "supported emulations:"
 	  # that means it is gnuoldld.
-	  echo "$ld_help_string" | grep >/dev/null 2>&1 "supported emulations:"
-	  test $? != 0 && echo "${UNAME_MACHINE}-pc-linux-gnuoldld" && exit 0
+	  test -z "$ld_supported_emulations" \
+	    && echo "${UNAME_MACHINE}-pc-linux-gnuoldld" && exit 0
 
 	  case "${UNAME_MACHINE}" in
 	  i?86)

  reply	other threads:[~2000-10-03 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-03 13:44 config.sub Richard Kenner
2000-10-03 13:57 ` Rod Stewart [this message]
2000-10-04  1:20 ` config.sub Akim Demaille
2002-04-25 15:13 config.sub Mark Mitchell
2002-04-25 15:23 ` config.sub Hans-Peter Nilsson
2002-04-25 15:39   ` config.sub Mark Mitchell

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=Pine.LNX.4.21.0010031646280.18110-100000@dystopia.lab43.org \
    --to=stewart@lab43.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).