From: Keith Owens <kaos@ocs.com.au>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: ide-probe.c:400: `rtc_lock' undeclared and /lib/modules/..../build
Date: Wed, 08 Nov 2000 14:59:42 +1100 [thread overview]
Message-ID: <6444.973655982@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 07 Nov 2000 21:48:59 CDT." <Pine.LNX.4.21.0011072148270.10929-100000@asdf.capslock.lan>
On Tue, 7 Nov 2000 21:48:59 -0500 (EST),
"Mike A. Harris" <mharris@opensourceadvocate.org> wrote:
>On Tue, 7 Nov 2000, Alan Cox wrote:
>>Actually they do. I agree that it wants sorting. Im just wondering what the
>>best approach is - maybe check modutils rev and only add the link if its high
>>enough ?
>
>What if build-machine != machine-kernel-was-built-for?
Then you are SOL, but that is a generic cross compile problem. Anybody
doing cross compile has to do extra steps to copy the results to the
other machine and they can take care of problems like the build symlink
themselves. The patch in 2.2.18-pre20 fixes the problem for local
compiles, which are 95%+ (SWAG) of the compiles.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 2:48 ide-probe.c:400: `rtc_lock' undeclared and /lib/modules/..../build Mike A. Harris
2000-11-08 3:59 ` Keith Owens [this message]
2000-11-08 8:35 ` Mike A. Harris
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 0:20 Tomasz Motylewski
2000-11-07 0:24 ` Mark Cooke
2000-11-07 3:24 ` Keith Owens
2000-11-07 12:11 ` Alan Cox
2000-11-07 13:21 ` Keith Owens
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=6444.973655982@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mharris@opensourceadvocate.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