From: Josh Huber <huber@mclx.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: problems about __cli()
Date: Thu, 20 Jul 2000 11:44:23 -0400 [thread overview]
Message-ID: <20000720114423.A20249@mclx.com> (raw)
In-Reply-To: <200007201345.OAA29151@hyperion.valhalla.net>; from iain@sandoe.co.uk on Thu, Jul 20, 2000 at 02:45:56PM +0100
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Thu, Jul 20, 2000 at 02:45:56PM +0100, Iain Sandoe wrote:
> I guess I *must* have one of those broken derivatives... and it doesn't work
> for me without that step... Admittedly, this is mostly an issue between
> 2.2.xx and 2.4.0 - but I do have to remember to change it back between
> whiles... a better way would be ?
Well...hmm, what doesn't work? You mean you can't build a kernel
unless you make /usr/src/linux point to the kernel source you're
building? This is odd, as I haven't done that...ever! In fact,
there's no directories in /usr/src on my machine.
I'm confused, as I've built many kernels on a redhat box here (intel,
but that shouldn't matter) without every updating the symlink, or
using /usr/src to build inside.
I tend to have very large amounts of kernel source laying around, and
I don't like to clutter my /usr partition with them...
--
Josh
6B21489A | GnuPG ID/Fingerprint | huber@mclx.com |
61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2000-07-20 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 13:45 problems about __cli() Iain Sandoe
2000-07-20 15:44 ` Josh Huber [this message]
2000-07-22 14:10 ` Geert Uytterhoeven
2000-07-22 18:11 ` Martin Costabel
2000-07-24 12:19 ` Josh Huber
2000-07-24 15:01 ` Jeff Garzik
2000-07-21 14:15 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2000-07-21 14:37 Iain Sandoe
2000-07-20 9:19 Iain Sandoe
2000-07-20 12:55 ` Josh Huber
2000-07-20 13:36 ` Michael Schmitz
2000-07-20 7:29 Rolf Liu
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=20000720114423.A20249@mclx.com \
--to=huber@mclx.com \
--cc=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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).