From: Jeff Garzik <jgarzik@pobox.com>
To: Joshua Kwan <joshk@triplehelix.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [gmulas@ca.astro.it: kernel-source-2.4.27: libata.o not compiled as module]
Date: Sat, 28 Aug 2004 22:30:50 -0400 [thread overview]
Message-ID: <41313FDA.6080009@pobox.com> (raw)
In-Reply-To: <20040829021638.GA29207@darjeeling.triplehelix.org>
Joshua Kwan wrote:
> forwarded 268188 jgarzik@pobox.com
> thanks
>
> Hi Jeff,
>
> It seems that libata.o isn't getting built when some drivers depending
> on libata are built as modules and others as built in, on 2.4.27. If
> they're either all built in, or all modules, everything builds fine.
>
> Would you have an idea on this matter?
> CONFIG_SCSI_SATA=y
> CONFIG_SCSI_SATA_SVW=m
> CONFIG_SCSI_SATA_PROMISE=m
> CONFIG_SCSI_SATA_SX4=m
> CONFIG_SCSI_SATA_SIL=m
> CONFIG_SCSI_SATA_SIS=m
> CONFIG_SCSI_SATA_VIA=m
> CONFIG_SCSI_SATA_VITESSE=y
Everything is working just fine, from looking at the output.
CONFIG_SCSI_SATA_VITESSE is set to 'y', which means that libata is built
into the kernel rather than as a module, because
CONFIG_SCSI_SATA_VITESSE is built into the kernel, and libata is a
dependency.
Because the dependency (libata.o) is built into the kernel, no kernel
module will be produced.
Jeff
next prev parent reply other threads:[~2004-08-29 2:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 2:16 [gmulas@ca.astro.it: kernel-source-2.4.27: libata.o not compiled as module] Joshua Kwan
2004-08-29 2:30 ` Jeff Garzik [this message]
2004-08-29 2:51 ` Joshua Kwan
2004-08-29 3:06 ` Jeff Garzik
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=41313FDA.6080009@pobox.com \
--to=jgarzik@pobox.com \
--cc=joshk@triplehelix.org \
--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.