All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Compile warning...
Date: Thu, 15 Apr 1999 17:52:08 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-92419958220068@msgid-missing> (raw)

When I try to build the current CVS tree, I get a error like 

gargleblaster:/usr/src/linux$ make
sed: -e expression #1, char 37: Unknown option to 's'
rm -f include/asm

It seems to be coming from arch/sparc64/Makefile line 23 , 

MAKEOVERRIDES   := $(shell echo "$(MAKEOVERRIDES)" | sed 's CC=$(CC)
CC=$(CC)\\\ -D__KERNEL__\\\ -I$(TOPDIR)/include ')

Which looks like its not pertenant to anything else, at all, anywhere (I
just grepped the whole source tree for MAKEOVERRIDES ;)

Can we just take this out?

Here's the patch, because I know I'm lazy and I'll assume the rest of the
world is too...

--- arch/sparc64/Makefile.old   Thu Apr 15 13:51:13 1999
+++ arch/sparc64/Makefile       Thu Apr 15 13:51:25 1999
@@ -20,7 +20,6 @@
 
 ifneq ($(CC_HAS_ARGS),y)
 TMP = $(shell echo sed \'s CC=$(CC) CC=$(CC)\\\ -D__KERNEL__\\\
-I$(TOPDIR)/include \') > /tmp/overrides)
-MAKEOVERRIDES  := $(shell echo "$(MAKEOVERRIDES)" | sed 's CC=$(CC)
CC=$(CC)\\\ -D__KERNEL__\\\ -I$(TOPDIR)/include ')
 override CC    := $(CC) -D__KERNEL__ -I$(TOPDIR)/include
 endif

 -- Peter

"Good night, Mrs. Calabash, wherever you are."
		-- Armstrong

             reply	other threads:[~1999-04-15 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-15 17:52 Peter Jones [this message]
1999-04-15 20:21 ` Compile warning David Miller
1999-04-15 22:03 ` Peter Jones
2007-10-26 13:25 compile warning Sergej Stepanov
2007-10-26 15:58 ` Kumar Gala
2007-10-30  7:43   ` Sergej Stepanov
2007-10-30  9:05     ` Arnd Bergmann
2009-10-01  9:18 Compile warning Fasiha Ashraf
2009-10-02  9:08 ` Ferenc Wagner
2011-07-28 16:03 Steve French

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=marc-linux-ultrasparc-92419958220068@msgid-missing \
    --to=pjones@redhat.com \
    --cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.