From: Miles Lane <miles.lane@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test2-bk3 (linus' tree) -- drivers/net/3c59x.c:534: error: `WNOOXCVR_PWR' undeclared here (not in a function)
Date: Mon, 4 Aug 2003 08:48:41 -0700 [thread overview]
Message-ID: <200308040848.41908.miles.lane@comcast.net> (raw)
CC [M] drivers/net/3c59x.o
drivers/net/3c59x.c:534: error: `WNOOXCVR_PWR' undeclared here (not in a
function)
drivers/net/3c59x.c:534: error: initializer element is not constant
drivers/net/3c59x.c:534: error: (near initialization for
`vortex_info_tbl[23].drv_flags')
drivers/net/3c59x.c:534: error: initializer element is not constant
drivers/net/3c59x.c:534: error: (near initialization for
`vortex_info_tbl[23]')
drivers/net/3c59x.c:536: error: initializer element is not constant
drivers/net/3c59x.c:536: error: (near initialization for
`vortex_info_tbl[24]')
drivers/net/3c59x.c:539: error: initializer element is not constant
Gnu C 3.3.1
Gnu make 3.80
util-linux 2.11z
mount 2.11x
e2fsprogs 1.32
pcmcia-cs 3.2.3
PPP 2.4.1
nfs-utils 1.0.5
Linux C Library 2.3.1
Dynamic linker (ldd) 2.3.1
Procps 3.1.6
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.0
GNU ld version 2.14 20030612
CONFIG_PPC=y
CONFIG_PPC32=y
CONFIG_6xx=y
#
# IBM 4xx options
#
CONFIG_PM=y
# CONFIG_8260 is not set
CONFIG_GENERIC_ISA_DMA=y
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_MULTIPLATFORM=y
CONFIG_PPC_CHRP=y
CONFIG_PPC_PMAC=y
CONFIG_PPC_PREP=y
CONFIG_PPC_OF=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
CONFIG_ALTIVEC=y
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_MACE is not set
# CONFIG_BMAC is not set
# CONFIG_OAKNET is not set
# CONFIG_HAPPYMEAL is not set
CONFIG_SUNGEM=m
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=m
CONFIG_TYPHOON=m
next reply other threads:[~2003-08-04 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 15:48 Miles Lane [this message]
2003-08-04 15:58 ` 2.6.0-test2-bk3 (linus' tree) -- drivers/net/3c59x.c:534: error: `WNOOXCVR_PWR' undeclared here (not in a function) Maciej Soltysiak
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=200308040848.41908.miles.lane@comcast.net \
--to=miles.lane@comcast.net \
--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