From: "Art Wagner" <awagner@qwest.net>
To: "alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 2.4.2-ac25 Compile error in es1370.c
Date: Mon, 26 Mar 2001 17:21:49 -0700 [thread overview]
Message-ID: <3ABFDD1D.8DE07D1D@qwest.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 174 bytes --]
Alan;
I got the attached compile error in /drivers/sound/es1370.c.
If any further information might be helpful please e-mail me or
post to LKML.
Art Wagner
awagner@qwest.net
[-- Attachment #2: make_modules-2.4.2-ac25-1.log_clip --]
[-- Type: text/plain, Size: 1106 bytes --]
make[2]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/scsi'
make[2]: Entering directory `/usr/src/linux-2.4.2-ac/drivers/video'
make -C aty modules
make[3]: Entering directory `/usr/src/linux-2.4.2-ac/drivers/usb/storage'
ld -m elf_i386 -r -o usb-storage.o scsiglue.o protocol.o transport.o usb.o initializers.o debug.o freecom.o
make[3]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/usb/storage'
make[2]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/usb'
make[3]: Entering directory `/usr/src/linux-2.4.2-ac/drivers/video/aty'
make[3]: Nothing to be done for `modules'.
make[3]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/video/aty'
make[2]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/video'
es1370.c: In function `es1370_probe':
es1370.c:2667: structure has no member named `trigger'
es1370.c:2667: structure has no member named `read'
make[2]: *** [es1370.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers/sound'
make[1]: *** [_modsubdir_sound] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.2-ac/drivers'
make: *** [_mod_drivers] Error 2
reply other threads:[~2001-03-27 0:23 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=3ABFDD1D.8DE07D1D@qwest.net \
--to=awagner@qwest.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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