From: Sebastian Roth <xsebbi@gmx.de>
To: davej@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH][2.5.3-dj4] Compile Error at 8139too.c
Date: Sat, 9 Feb 2002 10:48:44 +0100 [thread overview]
Message-ID: <200202091029.30256@xsebbi.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Hi there,
just a compile error:
gcc -D__KERNEL__ -I/usr/src/linux-2.5/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4
-DKBUILD_BASENAME=8139too -c -o 8139too.o 8139too.c
8139too.c:167: redefinition of `debug'
8139too.c:164: `debug' previously defined here
make[3]: *** [8139too.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.5/drivers/net'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.5/drivers/net'
make[1]: *** [_subdir_net] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5/drivers'
make: *** [_dir_drivers] Error 2
This patch solves the problem:
--- linux-2.5/drivers/net/8139too.c Sat Feb 9 10:44:11 2002
+++ linux-beta/drivers/net/8139too.c Sat Feb 9 10:44:50 2002
@@ -163,9 +163,6 @@
/* bitmapped message enable number */
static int debug = -1;
-/* bitmapped message enable number */
-static int debug = -1;
-
/* Size of the in-memory receive ring. */
#define RX_BUF_LEN_IDX 2 /* 0==8K, 1==16K, 2==32K, 3==64K */
#define RX_BUF_LEN (8192 << RX_BUF_LEN_IDX)
patch is against 2.5.3-dj4
Bye,
Sebastian
[-- Attachment #2: 8139patch --]
[-- Type: text/x-diff, Size: 423 bytes --]
--- linux-2.5/drivers/net/8139too.c Sat Feb 9 10:44:11 2002
+++ linux-beta/drivers/net/8139too.c Sat Feb 9 10:44:50 2002
@@ -163,9 +163,6 @@
/* bitmapped message enable number */
static int debug = -1;
-/* bitmapped message enable number */
-static int debug = -1;
-
/* Size of the in-memory receive ring. */
#define RX_BUF_LEN_IDX 2 /* 0==8K, 1==16K, 2==32K, 3==64K */
#define RX_BUF_LEN (8192 << RX_BUF_LEN_IDX)
reply other threads:[~2002-02-09 9:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200202091029.30256@xsebbi.de \
--to=xsebbi@gmx.de \
--cc=davej@suse.de \
--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