From 0a7b7709ebf8c7d7250700e367bc685dcdeecb6f Mon Sep 17 00:00:00 2001 From: Jim Wilson Date: Tue, 16 Mar 1993 12:15:00 -0800 Subject: [PATCH] (CFLAGS, LIBGCC2_CFLAGS): Delete overrides and comment why they were wrong. From-SVN: r3761 --- gcc/config/m68k/x-apollo68 | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/gcc/config/m68k/x-apollo68 b/gcc/config/m68k/x-apollo68 index 958259ac7e6..b7261ebb53e 100644 --- a/gcc/config/m68k/x-apollo68 +++ b/gcc/config/m68k/x-apollo68 @@ -5,13 +5,8 @@ CC=cc -g -A nansi -A cpu,3000 -A runtype,bsd4.3 -A systype,any -DSHORT_ENUM_BUG OLDCC=cc -g -A nansi -A cpu,3000 -A runtype,bsd4.3 -A systype,any -DSHORT_ENUM_BUG -# Makefile.in has debugging turned on: -# -# CFLAGS = -g -# LIBGCC2_CFLAGS = -O2 $(GCC_CFLAGS) -g1 -# -# but that's not supported on the Apollo yet, so we'd better avoid -# the warnings. - -CFLAGS = -LIBGCC2_CFLAGS = -O2 $(GCC_CFLAGS) +# This used to redefine CFLAGS and LIBGCC2_CFLAGS to eliminate the unsupported +# -g flag from both macros. This gives an undebugable stage1 compiler which +# is bad, and it also does the wrong thing if we are cross compiling to a +# target which does support debugging. There is currently no way to avoid +# the -g option that doesn't break something else. -- 2.30.2