From: "Carey M. Drake" <carey.drake@oracle.com>
To: James Simmons <jsimmons@suse.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Network error
Date: Wed, 08 Nov 2000 16:03:11 -0500 [thread overview]
Message-ID: <3A09BF8F.6AC771D3@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011081258310.259-100000@euclid.oak.suse.com>
Guess: you're using RedHat 7.0 (or somehow else are using a "new"
version of gcc).
Either use make cc=kgcc for redhat or downgrade gcc to a supported
version.
James Simmons wrote:
>
> Something I seen on a lug. Anyone have a patch for this?
>
> I'm trying to compile a 2.2.17 kernel. When I do a make bzImage, I get
> this error. It seems to be centering on networking areas (nfs, svclock,
> tcp, etc.)
>
> tcp_input.c:1393:52: warning: pasting would not give a valid preprocessing
> token
> tcp_input.c:1441:85: warning: pasting would not give a valid preprocessing
> token
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
C.
------------------------------------------------------------------------------
When in doubt, poke it with a stick
Disclaimer: the above is the author's personal opinion and is not the
opinion
or policy of his employer or of the little green men that have been
following
him all day.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 20:59 Network error James Simmons
2000-11-08 21:03 ` Carey M. Drake [this message]
2000-11-08 22:21 ` Andre Tomt
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=3A09BF8F.6AC771D3@oracle.com \
--to=carey.drake@oracle.com \
--cc=jsimmons@suse.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox