From: offer@sgi.com (richard offer)
To: linux-kernel@vger.kernel.org
Subject: Re: build -->/usr/src/linux
Date: Mon, 9 Apr 2001 16:01:06 -0700 [thread overview]
Message-ID: <10104091601.ZM401478@sgi.com> (raw)
In-Reply-To: <9aqmgo$8f6ol$1@fido.engr.sgi.com>
In-Reply-To: <3AD079EA.50DA97F3@rcn.com> <20010408161620.A21660@flint.arm.linux.org.uk> <3AD0A029.C17C3EFC@rcn.com>
In article <9aqmgo$8f6ol$1@fido.engr.sgi.com> you write:
>In article <3AD0A029.C17C3EFC@rcn.com>,
>Marvin Stodolsky <stodolsk@rcn.com> wrote:
>>Thanks for responding. But I would still like to understand what the
>>functionality is of the build --> /usr/src/linuc. Is it dispensable,
>>once the module tree has been installed?
>
>It's needed for modules that are distributed sperately, so that
>they can use cc -I /lib/modules/`uname -r`/build/include
>
>Or even
>
> l=`pwd`
> cd /lib/modules/`uname -r`/build
> make $l/module.o
>
>.. but there should be a cleaner way to get at the CFLAGS used
>to compile the kernel.
Ahhhh. Not again.
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...
>
>Mike.
richard.
-----------------------------------------------------------------------
Richard Offer Technical Lead, Trust Technology.
"Specialization is for insects"
__________________________________________http://reality.sgi.com/offer/
-----------------------------------------------------------------------
Richard Offer Technical Lead, Trust Technology.
"Specialization is for insects"
__________________________________________http://reality.sgi.com/offer/
next prev parent reply other threads:[~2001-04-09 22:58 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 [this message]
2001-04-10 14:08 ` Jamie Lokier
2001-04-10 16:36 ` richard offer
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=10104091601.ZM401478@sgi.com \
--to=offer@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.