[ale] Regarding Kernel Operations
Joseph A Knapka
jknapka at earthlink.net
Tue Jul 16 11:03:50 EDT 2002
Geoffrey wrote:
>
> stephen wrote:
> > On Mon, Jul 15, 2002 at 09:41:55PM -0600, Joseph A Knapka wrote:
> >
> >>Jeff Hubbs wrote:
> >>
> >>>When you do a kernel/modules compile, from where all does source, etc.
> >>>get pulled to make the final result? Reason I ask is, if you want to
> >>>do your compiling on another machine to speed up the process, what all
> >>>needs to make the trip? Is it just the kernel source tree or are there
> >>>things in /usr/lib or elsewhere that would have to be brought over and
> >>>pointed to somehow?
> >>>
> >>The kernel is built, top to bottom, using only the code in the
> >>kernel source tree.
> >>
> >
> > Actually, there are some source files in scripts/, such as your mkdep
> > utility, and other utilities under some of the arch/ branches for
> > converting elf to a.out and making tftp boot images that include headers
> > from libc.
>
> But scripts and arch are under the /usr/src/linux tree.
>
I'm sorry, stephen is correct. For example, "make xconfig"
actually builds a small C utility that's used to present
the config UI and construct the config file; that
process depends on the presence of the libc and Tcl/Tk
header files installed on your system.
However, the code that actually gets *linked into the
kernel image* resides entirely under /usr/src/linux.
-- Joe
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list