From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Tried to run 2.6.0-test1
Date: Mon, 21 Jul 2003 15:56:30 +0900 [thread overview]
Message-ID: <0c3201c34f55$4e949280$64ee4ca5@DIAMONDLX60> (raw)
Again I cannot keep up with the mailing list. If anyone wishes to advise or
has questions, please kindly contact me directly.
In addition to my previous message quoting myself, I lied yet again:
> I've downloaded modutils-2.4.21-18.src.rpm from Rusty Russell's directory
[...]
> Odds are I can probably gunzip and tar and compile the new modutils, but
> will the resulting executables get installed into the right places without
> using the rpm command and its spec file, I'm not sure I want to chance it.
I read the two README files. BOTH OF THE GZIPPED TARBALLS
PRODUCE THE SAME EXECUTABLE FILENAMES, such as insmod.
If I can get both of them to build, how can I guess which one to install?
Besides, I tried building module-init-tools-0.9.11a even after its configure
script failed. There are a lot more differences than just the type of cpu,
from the compilation options when trying "rpm --rebuild". For example no -D
options for combining various stuff, no URL to explain tainting, etc. Also
this one's "make install" doesn't install the lsmod command.
I really really lied. I'll never figure out how to build these things
without help. As I understand it, all I need at this point is the new
modutils for execution on an i586.
next reply other threads:[~2003-07-21 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 6:56 Norman Diamond [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-21 6:23 Tried to run 2.6.0-test1 Norman Diamond
2003-07-21 6:52 ` Brett
2003-07-21 7:06 ` Norman Diamond
2003-07-21 7:18 ` Brett
2003-07-21 10:07 ` Gene Heskett
2003-07-20 15:03 Norman Diamond
2003-07-20 15:26 ` Valdis.Kletnieks
2003-07-20 15:48 ` Norman Diamond
2003-07-20 16:02 ` Diego Calleja García
2003-07-20 19:20 ` Gabor MICSKO
2003-07-21 5:48 ` Norman Diamond
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='0c3201c34f55$4e949280$64ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox