Hi
Luis Useche wrote:
Hi Guys,
I want to modify OpenSolaris kernel for some project. I have been struggling
really hard to compile the OpenSolaris kernel 2 days now with no success. I am
doing this using the last release of OpenSolaris Indiana 2009.06. My steps:
1) clone the code with hg
2) Install all requirements to build ON with the package manager (the package
is called onet)
3) Install the SunStudio
4) Build the environment with bldenv
bldenv just sets up the environment variables to influence the
makefiles, it does nothing to the workspace itself.
5) cd usr/src/uts/; dmake all
As bldenv utters, the top-level target 'setup' is available and should be
used before jumping inyo uts etc and building. So you'd normally do something
like the following after entering your bldenv shell:
cd $SRC
dmake setup
(that target was actually failing a few builds back, not sure if it
is fixed yet; if it fails then cd $SRC/tools; dmake install before
the dmake setup in $SRC).
The setup target will cause your proto area to be fleshed out with
empty directories and will install and build where necessary all header
files (equivalent to dmake install_h run in uts, lib etc).
After long time compiling, the compiler raise an error in the file ncall.c stating
that the header <sys/nsctl/nsvers.h> does not exist.
(gav...@enogas:/gas/ws/onnv-local/usr/src )-> hg manifest | grep nsvers.h
usr/src/uts/common/avs/ns/nsctl/nsvers.h
So the setup target will put that in the right place in your
proto area ready for further compile (the bldenv script
sets ENVCPPFLAGS1 to find headers from your proto area).
The other approach is to use 'nightly' to build the whole thing
from scratch the first time, then use bldenv thereafter
for incremental work.
Gavin
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code