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

On Thu, 15 Apr 1999, David Miller wrote:

>    Date: 	Thu, 15 Apr 1999 13:52:08 -0400 (EDT)
>    From: Peter Jones <pjones@redhat.com>
> 
>    gargleblaster:/usr/src/linux$ make
>    sed: -e expression #1, char 37: Unknown option to 's'
>    rm -f include/asm
> 
> I don't get this...  The first thing I do after a beta RH install is
> to cvs checkout and build a kernel, so I'd notice something like this,
> or else it goes by in the build output so fast I don't catch it :-)

Well, I guess I'll look harder for having done something stupid then ;)

>    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?
> 
> MAKEOVERRIDES is an internal 'make' variable, it is used even though
> it is not explicitly referenced.

Oh, ok.  I guess I'll have to pull it appart some more and figure out why
my system is doing odd things with it, and read some more make docs...

> Later,
> David S. Miller
> davem@redhat.com

 -- Peter

"An age is called dark not because the light fails to shine, but because
people refuse to see it."
		-- James Michener, "Space"

  parent reply	other threads:[~1999-04-15 22:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-15 17:52 Compile warning Peter Jones
1999-04-15 20:21 ` David Miller
1999-04-15 22:03 ` Peter Jones [this message]
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-92421402300529@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.