From: Greg KH <greg@kroah.com>
To: d_vangreg <d.vangreg@inwind.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: COMPILATION-BUGS_KERNEL-2.5.18
Date: Tue, 28 May 2002 10:55:23 -0700 [thread overview]
Message-ID: <20020528175523.GG11993@kroah.com> (raw)
In-Reply-To: <20020527142306Z316627-22651+61956@vger.kernel.org>
On Mon, May 27, 2002 at 04:32:42PM +0200, d_vangreg wrote:
> #################
>
> COMPILATION-BUG-3 encountered while executing: 'make modules'
> ........................
> /opt/gcc304a/bin/gcc -D__KERNEL__ -I/usr/src/linux-2.5.18/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=athlon -DMODULE -DMODVERSIONS -include
> /usr/src/linux-2.5.18/include/linux/modversions.h
> -DKBUILD_BASENAME=usbvideo -DEXPORT_SYMTAB -c -o usbvideo.o usbvideo.c
> usbvideo.c: In function `usbvideo_StartDataPump':
> usbvideo.c:1906: structure has no member named `next'
> usbvideo.c:1908: structure has no member named `next'
> make[3]: *** [usbvideo.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.5.18/drivers/usb/media'
> make[2]: *** [_modsubdir_media] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.5.18/drivers/usb'
> make[1]: *** [_modsubdir_usb] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.5.18/drivers'
> make: *** [_mod_drivers] Error 2
>
>
> PROPOSED-SOLUTION-3:
> replacing string '->next' with string '->urb_list.next'
> in file: linux/drivers/usb/media/usbvideo.c lines: 1906, 1908
Eeek, NO!
The ->next field is now gone. The driver needs to be changed due to
this core USB change. See the cpia and audio USB drivers for how to do
this properly.
thanks,
greg k-h
prev parent reply other threads:[~2002-05-28 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 14:32 COMPILATION-BUGS_KERNEL-2.5.18 d_vangreg
2002-05-28 17:55 ` Greg KH [this message]
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=20020528175523.GG11993@kroah.com \
--to=greg@kroah.com \
--cc=d.vangreg@inwind.it \
--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