From: Louis Garcia <louisg00@bellsouth.net>
To: linux-kernel@vger.kernel.org
Subject: USB compile error with latest 2.5-bk
Date: 23 Mar 2003 18:34:31 -0500 [thread overview]
Message-ID: <1048462471.1739.1.camel@tiger> (raw)
I'm running RH phoebe beta
gcc -Wp,-MD,drivers/usb/core/.hcd.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=pentium4
-Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc
-iwithprefix include -DMODULE -DKBUILD_BASENAME=hcd
-DKBUILD_MODNAME=usbcore -c -o drivers/usb/core/.tmp_hcd.o
drivers/usb/core/hcd.c
drivers/usb/core/hcd.c:124: parse error before '>>' token
drivers/usb/core/hcd.c:124: initializer element is not constant
drivers/usb/core/hcd.c:124: (near initialization for
`usb2_rh_dev_descriptor[12]')
drivers/usb/core/hcd.c:124: parse error before '>>' token
drivers/usb/core/hcd.c:124: initializer element is not constant
drivers/usb/core/hcd.c:124: (near initialization for
`usb2_rh_dev_descriptor[13]')
drivers/usb/core/hcd.c:147: parse error before '>>' token
drivers/usb/core/hcd.c:147: initializer element is not constant
drivers/usb/core/hcd.c:147: (near initialization for
`usb11_rh_dev_descriptor[12]')
drivers/usb/core/hcd.c:147: parse error before '>>' token
drivers/usb/core/hcd.c:147: initializer element is not constant
drivers/usb/core/hcd.c:147: (near initialization for
`usb11_rh_dev_descriptor[13]')
make[4]: *** [drivers/usb/core/hcd.o] Error 1
make[3]: *** [drivers/usb/core] Error 2
make[2]: *** [drivers/usb] Error 2
make[1]: *** [drivers] Error 2
make: *** [all] Error 2
next reply other threads:[~2003-03-23 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 23:34 Louis Garcia [this message]
2003-03-24 9:53 ` USB compile error with latest 2.5-bk Greg KH
2003-03-24 14:04 ` Alan Cox
2003-03-25 4:33 ` Louis Garcia
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=1048462471.1739.1.camel@tiger \
--to=louisg00@bellsouth.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 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.