From: "Toralf Förster" <toralf.foerster@gmx.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: djwong@us.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: build #308 failed for 2.6.23-rc1-gd941cf5 in linux/./drivers/scsi/libsas/sas_ata.c
Date: Tue, 31 Jul 2007 16:13:24 +0200 [thread overview]
Message-ID: <200707311613.24709.toralf.foerster@gmx.de> (raw)
In-Reply-To: <1185635256.11492.18.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 3181 bytes --]
Am Samstag, 28. Juli 2007 17:07 schrieb James Bottomley:
> On Fri, 2007-07-27 at 12:53 +0200, Toralf Förster wrote:
> > Hello,
> >
> > the build with the attached .config failed, make ends with:
> > ...
> > CHK include/linux/compile.h
> > UPD include/linux/compile.h
> > CC init/version.o
> > LD init/built-in.o
> > LD .tmp_vmlinux1
> > drivers/built-in.o: In function `sas_queuecommand':
> > (.text+0x932af): undefined reference to `ata_sas_queuecmd'
> > drivers/built-in.o: In function `sas_slave_configure':
> > (.text+0x934a4): undefined reference to `ata_sas_slave_configure'
> > drivers/built-in.o: In function `sas_target_destroy':
> > (.text+0x92317): undefined reference to `ata_sas_port_destroy'
> > drivers/built-in.o: In function `sas_ioctl':
> > (.text+0x92fa4): undefined reference to `ata_scsi_ioctl'
> > drivers/built-in.o: In function `sas_slave_destroy':
> > (.text+0x92fcd): undefined reference to `ata_port_disable'
> > drivers/built-in.o: In function `sas_slave_alloc':
> > (.text+0x9307f): undefined reference to `ata_sas_port_init'
> > drivers/built-in.o: In function `sas_ata_init_host_and_port':
> > (.text+0x942c6): undefined reference to `ata_host_init'
> > drivers/built-in.o: In function `sas_ata_init_host_and_port':
> > (.text+0x942d4): undefined reference to `ata_sas_port_alloc'
> > drivers/built-in.o: In function `sas_ata_qc_issue':
> > sas_ata.c:(.text+0x9445d): undefined reference to `ata_tf_to_fis'
> > drivers/built-in.o: In function `sas_ata_task_done':
> > sas_ata.c:(.text+0x9473c): undefined reference to `ata_tf_from_fis'
> > sas_ata.c:(.text+0x9479b): undefined reference to `ata_qc_complete'
> > drivers/built-in.o:(.data+0xafc0): undefined reference to `ata_port_disable'
> > drivers/built-in.o:(.data+0xafe8): undefined reference to `ata_noop_dev_select'
> > drivers/built-in.o:(.data+0xb008): undefined reference to `ata_noop_qc_prep'
> > drivers/built-in.o:(.data+0xb044): undefined reference to `ata_sas_port_start'
> > drivers/built-in.o:(.data+0xb048): undefined reference to `ata_sas_port_stop'
> > make: *** [.tmp_vmlinux1] Error 1
>
> This is a Kconfig cockup. If you have the libsas with ATA support, it
> needs libata to function. The problem is that if you compile in libsas,
> you can't build libata as a module (however, vice versa you can).
>
> About the only way I can think to code this in current Kconfig is the
> attached rather ugly code.
>
> James
>
> diff --git a/drivers/scsi/libsas/Kconfig b/drivers/scsi/libsas/Kconfig
> index 3a3c1ac..c01a40d 100644
> --- a/drivers/scsi/libsas/Kconfig
> +++ b/drivers/scsi/libsas/Kconfig
> @@ -32,7 +32,8 @@ config SCSI_SAS_LIBSAS
>
> config SCSI_SAS_ATA
> bool "ATA support for libsas (requires libata)"
> - depends on SCSI_SAS_LIBSAS && ATA
> + depends on SCSI_SAS_LIBSAS
> + depends on ATA = y || ATA = SCSI_SAS_LIBSAS
> help
> Builds in ATA support into libsas. Will necessitate
> the loading of libata along with libsas.
>
>
This patch works fine, the build now finishes succesfully with that .config file.
--
MfG/Sincerely
Toralf Förster
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-07-31 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 10:53 build #308 failed for 2.6.23-rc1-gd941cf5 in linux/./drivers/scsi/libsas/sas_ata.c Toralf Förster
2007-07-28 15:07 ` James Bottomley
2007-07-31 14:13 ` Toralf Förster [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=200707311613.24709.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=James.Bottomley@steeleye.com \
--cc=djwong@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox