From: Martijn Uffing <mp3project@cam029208.student.utwente.nl>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: linux-kernel@vger.kernel.org, <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Russell Coker <russell@coker.com.au>
Subject: Re: Linux 2.4.21-rc3
Date: Fri, 23 May 2003 15:30:14 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0305231516470.29275-100000@cam029208.student.utwente.nl> (raw)
In-Reply-To: <3ECE1DBF.5090602@gmx.net>
On Fri, 23 May 2003, Carl-Daniel Hailfinger wrote:
> Martijn Uffing wrote:
> > Ave
> >
> > Modular ide is still broken in 2.4.21-rc3 with my config.
>
> IIRC, Alan said it is not suposed to work yet. However, if you're
> feeling brave (and have no valuable data), you can try to export these
> symbols to make depmod happy. (Please read on)
I found "o fix modular ide build and other makefile bug" in Changelog so
I thought to give it another try.
>
> > "make modules_install" gives a:
> >
> > depmod: *** Unresolved symbols in /lib/modules/2.4.21-rc3/kernel/drivers/ide/ide-disk.o
> > depmod: proc_ide_read_geometry
> > depmod: ide_remove_proc_entries
> > depmod: *** Unresolved symbols in /lib/modules/2.4.21-rc3/kernel/drivers/ide/ide-probe.o
> > depmod: do_ide_request
> > depmod: ide_add_generic_settings
> > depmod: create_proc_ide_interfaces
> > depmod: *** Unresolved symbols in /lib/modules/2.4.21-rc3/kernel/drivers/ide/ide.o
> > depmod: ide_release_dma
> > depmod: ide_add_proc_entries
> > depmod: cmd640_vlb
> > depmod: ide_probe_for_cmd640x
> > depmod: ide_scan_pcibus
> > depmod: proc_ide_read_capacity
> > depmod: proc_ide_create
> > depmod: ide_remove_proc_entries
> > depmod: destroy_proc_ide_drives
> > depmod: proc_ide_destroy
> > depmod: create_proc_ide_interfaces
> >
> >
> no one can complain that the released kernel does not compile. Marcelo
> could just revert it for 2.4.22-pre then.
>
> This is mainly to keep the complaint level down.
>
>
> Regards,
> Carl-Daniel
>
Ehh 2.4.21-rc3 compiles fine with my config. It even runs fine! Only
modular ide won't work. But if the changes are to invasive for 2.4.21 I
can understand.
Greetz Mu
next prev parent reply other threads:[~2003-05-23 13:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 12:42 Linux 2.4.21-rc3 Martijn Uffing
2003-05-23 13:10 ` Carl-Daniel Hailfinger
2003-05-23 13:30 ` Martijn Uffing [this message]
2003-05-23 15:00 ` Matthias Andree
2003-05-26 17:11 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 14:00 Andrzej Krzysztofowicz
2003-05-26 17:53 ` Santiago Garcia Mantinan
2003-05-30 20:55 ` Krzysiek Taraszka
2003-05-30 20:23 ` Alan Cox
2003-05-23 7:00 Melchior FRANZ
2003-05-22 22:19 Marcelo Tosatti
2003-05-22 23:46 ` J.A. Magallon
2003-05-26 17:04 ` Alan Cox
2003-05-23 0:51 ` Barry K. Nathan
2003-05-23 5:32 ` Marc-Christian Petersen
2003-05-23 8:27 ` Benjamin Herrenschmidt
2003-05-26 13:16 ` Santiago Garcia Mantinan
2003-05-27 1:14 ` Jeff Chua
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=Pine.LNX.4.44.0305231516470.29275-100000@cam029208.student.utwente.nl \
--to=mp3project@cam029208.student.utwente.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=russell@coker.com.au \
/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;
as well as URLs for NNTP newsgroup(s).