From: Marvin Stodolsky <stodolsk@rcn.com>
To: linux-scsi@vger.kernel.org
Subject: PROBLEM:drivers/scsi: In function `sdebug_scatg2virt
Date: Sat, 13 Apr 2002 21:26:02 -0500 [thread overview]
Message-ID: <3CB8E8BA.5855149E@rcn.com> (raw)
[1.] scsi_debug.c:521: structure has no member named `address'
[2.] Compile with 2.5.7 sources fails within:
/usr/bin/make -C scsi modules
make[3]: Entering directory `/usr/src/Lnx/linux-2.5.7/drivers/scsi'
at subsection:
gcc -D__KERNEL__ -I/usr/src/Lnx/linux-2.5.7/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -DMODULE -DMODVERSIONS -include
/usr/src/Lnx/linux-2.5.7/include/linux/modversions.h
-DKBUILD_BASENAME=scsi_debug -c -o scsi_debug.o scsi_debug.c
scsi_debug.c: In function `sdebug_scatg2virt':
scsi_debug.c:521: structure has no member named `address'
scsi_debug.c:526: warning: control reaches end of non-void function
make[3]: *** [scsi_debug.o] Error 1
make[3]: Leaving directory `/usr/src/Lnx/linux-2.5.7/drivers/scsi'
make[2]: *** [_modsubdir_scsi] Error 2
make[2]: Leaving directory `/usr/src/Lnx/linux-2.5.7/drivers'
make[1]: *** [_mod_drivers] Error 2
make[1]: Leaving directory `/usr/
3) using
gcc --version 2.95.4
GNU Make version 3.79.
GNU ld version 2.12.90.0.1 20020307 Debian/GNU Linux
Compiling under a 2.4.18 kernel
=========
grep -v not /usr/src/linux/.config , SCSI section
#
# SCSI support
#
CONFIG_SCSI=m
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI low-level drivers
#
CONFIG_SCSI_DEBUG=m
next reply other threads:[~2002-04-14 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 2:26 Marvin Stodolsky [this message]
2002-04-14 18:13 ` PROBLEM:drivers/scsi: In function `sdebug_scatg2virt Douglas Gilbert
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=3CB8E8BA.5855149E@rcn.com \
--to=stodolsk@rcn.com \
--cc=linux-scsi@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.