linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob_Tracy)
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.38: modular IDE broken
Date: Tue, 24 Sep 2002 09:13:27 -0500 (CDT)	[thread overview]
Message-ID: <m17tqRL-0005khC@gherkin.frus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209231749050.13892-100000@chaos.physics.uiowa.edu> "from Kai Germaschewski at Sep 23, 2002 05:51:28 pm"

Kai Germaschewski wrote:
> ===== Makefile 1.5 vs edited =====
> --- 1.5/drivers/ide/Makefile	Wed Sep 18 20:11:21 2002
> +++ edited/Makefile	Mon Sep 23 17:50:05 2002
> @@ -24,7 +24,7 @@
>  obj-$(CONFIG_BLK_DEV_IDEDMA_PCI)	+= ide-dma.o
>  obj-$(CONFIG_BLK_DEV_ISAPNP)		+= ide-pnp.o
>  
> -ifeq ($(CONFIG_BLK_DEV_IDE),y)
> +ifdef CONFIG_BLK_DEV_IDE
>  obj-$(CONFIG_PROC_FS)			+= ide-proc.o
>  endif

I neglected to mention that the above patch (exactly the same, as it
turns out :-)) is how I forced the ide-proc.o build.  The brokenness
extends deeper.

Specific example: proc_ide_read_geometry has the requisite EXPORT_SYMBOL()
wrapper in ide-proc.c, yet, I still end up with proc_ide_read_geometry_R*
unresolved at depmod time.  In case anyone is wondering, I *did* do a
"make clean", manually cleaned out linux/include/modules to make *sure*
there wasn't any old cruft lying about, then ran "make dep && make bzImage &&
make modules && make modules_install".  The depmod output quoted below is
the result of all that.

> if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.38; fi
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide-disk.o
> depmod:         proc_ide_read_geometry_R50fed6f7
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide-floppy.o
> depmod:         proc_ide_read_geometry_R50fed6f7
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide-probe.o
> depmod:         do_ide_request
> depmod:         ide_add_generic_settings
> depmod:         create_proc_ide_interfaces_Rab2c600e
> depmod:         ide_bus_type
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide.o
> depmod:         proc_ide_create_Ra8e0f104
> depmod:         ide_remove_proc_entries_R5a5a621b
> depmod:         ide_add_proc_entries_Rce569c25
> depmod:         destroy_proc_ide_drives_Ra54f63e5
> depmod:         proc_ide_destroy_R35e1351c
> depmod:         bus_unregister
> depmod:         proc_ide_read_capacity_R46b2a30d
> depmod:         create_proc_ide_interfaces_Rab2c600e
> depmod:         ide_scan_pcibus
> make: *** [_modinst_post] Error 1

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

  reply	other threads:[~2002-09-24 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 21:28 Bob_Tracy
2002-09-23 22:51 ` Kai Germaschewski
2002-09-24 14:13   ` Bob_Tracy [this message]
2002-09-24 16:30     ` Kai Germaschewski
2002-09-26 16:10     ` Alan Cox
2002-09-27 20:37       ` Bob_Tracy
2002-09-27 22:41         ` Alan Cox

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=m17tqRL-0005khC@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=kai-germaschewski@uiowa.edu \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.5.38: modular IDE broken' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).