Haik Aftandilian writes: > A nice way to crawl before you walk would be to use the "nightly" script to > do a full build of the source tree. This will build the kernel and userland. > Using nightly is the easy way to build everything, and this builds everything > for your architecture. So all x86 drivers would be built when you run a > nightly build on x86. You don't have to run nightly, but it's a good way to > start. Afterwards, you can explore the source tree and build individual > drivers and modules.
Also good advice. Part of the background here is that Linux has a greater reliance (in general) on #ifdef than does Solaris. We've never had the assumption that if you wanted to turn a feature on you could "just recompile," so things that are options are run-time switches or tunables rather than compile-time configuration. In fact, #ifdef is discouraged as a way to accomplish many things. The one big counter-example is the difference between a DEBUG and a non-DEBUG kernel. But even that one helps prove the point, as it's such a famous and singular distinction that it's baked into the build process, and we don't have a good infrastructure to support many things like it. That Linux does have a substantial infrastructure in this area points to a philosophical difference between the two. Privately, I suggested that the original poster check out "Solaris Internals" and other books that discuss how the bits work. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
