From: Matthew Wilcox <matthew@wil.cx>
To: Abdelrahman <estr4ng3d@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI support broken in latest 2.4 kernel
Date: Tue, 24 Jul 2007 05:26:06 -0600 [thread overview]
Message-ID: <20070724112605.GG26883@parisc-linux.org> (raw)
In-Reply-To: <1185266014.28815.14.camel@localhost.localdomain>
On Tue, Jul 24, 2007 at 11:33:33AM +0300, Abdelrahman wrote:
> It seems impossible to compile the latest 2.4.35.6 kernel with the
> scsi_mod module and produce a usable system. I have used the attached
> config file and the normal compile procedure (make dep; make bzImage;
> make modules) and ended up with unloadable modules (unresolved symbols).
> I have tried both gcc 3.3 and 4.1. The same issue exists in at least
> 2.4.27 as well.
>
> Please advise if I can provide any further information which would aid
> in resolution.
Which symbols?
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2007-07-24 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 8:33 SCSI support broken in latest 2.4 kernel Abdelrahman
2007-07-24 11:26 ` Matthew Wilcox [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=20070724112605.GG26883@parisc-linux.org \
--to=matthew@wil.cx \
--cc=estr4ng3d@gmail.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;
as well as URLs for NNTP newsgroup(s).