public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "richard offer" <offer@sgi.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: build -->/usr/src/linux
Date: Tue, 10 Apr 2001 09:36:15 -0700	[thread overview]
Message-ID: <1010410093615.ZM1231@sgi.com> (raw)
In-Reply-To: Jamie Lokier <lk@tantalophile.demon.co.uk> "Re: build -->/usr/src/linux" (Apr 10,  4:08pm)
In-Reply-To: <3AD079EA.50DA97F3@rcn.com>  <20010408161620.A21660@flint.arm.linux.org.uk>  <3AD0A029.C17C3EFC@rcn.com>  <9aqmgo$8f6ol$1@fido.engr.sgi.com>  <10104091601.ZM401478@sgi.com>  <20010410160825.A20555@pcep-jamie.cern.ch>


* $ from lk@tantalophile.demon.co.uk at "10-Apr: 4:08pm" | sed "1,$s/^/* /"
*
*
* richard offer wrote:
* > uname does not always provide useful information (cross compiling). Even
* > if you're building the same ISA, you maybe in a chroot'ed environment.
* >
* > Can we please not assume that everybody only ever builds native...
*
* Nobody is assuming that.  If you're hard enough to do a cross compile,
* you can build external modules using "make KERNEL_RELEASE=2.4.2
* KERNEL_SOURCE=/home/jamie/cross_compiling/kernel ARCH=mips64" or
* whatever.

Applications make that assumption all the time.

Yes, this is the kernel mail list, but applications use kernel services. By
tacitly agreeing that you get the kernel headers from /lib/modules/`uname
-r`/build/include that's what people will code into their makefiles.

Saying "oh, but applications should do that" isn't much of a argument, as there
isn't a better way of working out where a set of kernel headers are.

And "oh but applications should be using /usr/include/" doesn't cut it. There
are times when you really do need to be able to build things outside of the
kernel tree that are kernel specific.

*
* -- Jamie
*

richard.


-----------------------------------------------------------------------
Richard Offer                         Technical Lead, Trust Technology.
"Specialization is for insects"
__________________________________________http://reality.sgi.com/offer/


  reply	other threads:[~2001-04-10 16:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9aqmgo$8f6ol$1@fido.engr.sgi.com>
2001-04-08 14:47 ` build -->/usr/src/linux Marvin Stodolsky
2001-04-08 15:16   ` Russell King
2001-04-08 17:30     ` Marvin Stodolsky
2001-04-08 21:49       ` Miquel van Smoorenburg
2001-04-08 23:01         ` Jamie Lokier
2001-04-09 11:29           ` Miquel van Smoorenburg
2001-04-09 15:02             ` Jamie Lokier
2001-04-09 23:01       ` richard offer
2001-04-10 14:08         ` Jamie Lokier
2001-04-10 16:36           ` richard offer [this message]
2001-04-10 16:42             ` Jamie Lokier
2001-04-10 16:52               ` richard offer
2001-04-10 17:04                 ` Jamie Lokier

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=1010410093615.ZM1231@sgi.com \
    --to=offer@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    /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