Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: binutils@sources.redhat.com
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com, dj@redhat.com
Subject: patches: config for m68k-apollo-bsd*, or not
Date: Sun, 10 Nov 2002 13:33:00 -0000	[thread overview]
Message-ID: <20021110213300.GA488@doctormoo> (raw)

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

All right.  It appears that out of all of gcc and src, m68k-apollo-bsd* 
(as opposed to m68k-apollo-sysv*) is supported potentially only by gas.  

I am strongly inclined to kill the top level configuration logic for it, 
because it is causing trouble in autoconfiscation.  This is the 
deapollo.diff patch.  I would like it approved for the gcc 3.4 basic 
improvements branch and subsequently for src when that branch lands.

If there are strong objections, the alternate patch apollo.diff updates 
the top level logic to allow the top level Makefile.in to be made 
autoconf-compatible.  But I prefer the first patch as it's simpler.

	* configure.in (m68k-apollo-bsd*): Drop support.

-or-
	* configure: Add hook for per-build-machine override of BISON.
	* configure.in: Use it for m68k-apollo-bsd*.

[-- Attachment #2: deapollo.diff --]
[-- Type: text/plain, Size: 1110 bytes --]

Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.177.4.5
diff -u -r1.177.4.5 configure.in
--- configure.in	10 Nov 2002 21:14:18 -0000	1.177.4.5
+++ configure.in	10 Nov 2002 21:26:46 -0000
@@ -943,16 +943,6 @@
     tentative_cc="cc -A ansi -A runtype,any -A systype,any -U__STDC__ -DUSG"
     host_makefile_frag="config/mh-apollo68"
     ;;
-  m68k-apollo-bsd*)
-    #None of the Apollo compilers can compile gas or binutils.  The preprocessor
-    # chokes on bfd, the compiler won't let you assign integers to enums, and
-    # other problems.  Defining CC to gcc is a questionable way to say "don't use
-    # the apollo compiler" (the preferred version of GCC could be called cc,
-    # or whatever), but I'm not sure leaving CC as cc is any better...
-    #CC=cc -A ansi -A runtype,any -A systype,any -U__STDC__ -DNO_STDARG
-    tentative_cc=gcc
-    host_makefile_frag="config/mh-a68bsd"
-    ;;
   m88k-dg-dgux*)
     tentative_cc="gcc -Wall -ansi -D__using_DGUX"
     host_makefile_frag="config/mh-dgux"

[-- Attachment #3: apollo.diff --]
[-- Type: text/plain, Size: 1301 bytes --]

? aix.diff
? apollo.diff
? p1.patch
? p2.patch
? p3.patch
? p4.patch
Index: configure
===================================================================
RCS file: /cvs/gcc/gcc/configure,v
retrieving revision 1.46.6.3
diff -u -r1.46.6.3 configure
--- configure	10 Nov 2002 21:14:18 -0000	1.46.6.3
+++ configure	10 Nov 2002 21:22:26 -0000
@@ -1037,7 +1037,8 @@
   AR_FOR_TARGET=${AR_FOR_TARGET}${extra_arflags_for_target}
   AS=as
   AS_FOR_TARGET='\$(USUAL_AS_FOR_TARGET)'
-  BISON='$(USUAL_BISON)'
+  # default to previously set bison: workaround for m68k-apollo-bsd
+  BISON=${BISON-'\$(USUAL_BISON)'}
   CC_FOR_BUILD='\$(CC)'
   DLLTOOL=dlltool
   DLLTOOL_FOR_TARGET='\$(USUAL_DLLTOOL_FOR_TARGET)'
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.177.4.5
diff -u -r1.177.4.5 configure.in
--- configure.in	10 Nov 2002 21:14:18 -0000	1.177.4.5
+++ configure.in	10 Nov 2002 21:22:32 -0000
@@ -103,6 +103,12 @@
 
 # per-target:
 
+# This is a irritating workaround for m68k-apollo-bsd,
+# which wants to use yacc for bison.
+case ${build} in
+  m68k-apollo-bsd*) BISON=yacc ;;
+esac
+
 # Define is_cross_compiler to save on calls to 'test'.
 is_cross_compiler=
 if test x"${host}" = x"${target}" ; then

             reply	other threads:[~2002-11-10 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10 13:33 Nathanael Nerode [this message]
2002-11-10 14:05 ` Zack Weinberg

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=20021110213300.GA488@doctormoo \
    --to=neroden@twcny.rr.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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