On Thursday, May 16, 2002, at 05:47 AM, Max Horn wrote:
> And don't forget that only people who actually have dual-processor > systems can test these modified build scripts. Thus, I won't add such > code to my packages (those that use GNU make anyway, which are not > all), because I would have to spend a lot of time to first research > whether a package is MP-compilation-clean, then I would need to get > some testers with dual processor machines to test it. According to this webpage http://www.linuxchix.org/content/courses/kernel_hacking/lesson3 After you've created the dependencies, build the kernel itself: On an x86: # make -j<number of jobs> bzImage On a PPC: # make -j<number of jobs> zImage Where <number of jobs> is two times the number of cpus in your system. So if you have a single cpu Pentium III, you'd do: # make -j2 bzImage What the "-j" argument tells the make program is to run that many jobs (commands in the Makefile) at once. "make" knows which jobs can be run at the same time and which jobs need to wait for other jobs to finish before they can run. Kernel compilation jobs spend enough time waiting for I/O (for example, reading the source file from disk) that running two of the jobs per processor results in the shortest compilation time. NOTE: If you get a compile error, run "make" with only one job so that it's easy to see where the error occurred. Otherwise, the error message will be hidden in the output from the other "make" jobs. Now, the scheduler in MacOSX differs from that in Linux, and the IO bottlenecks associated with compiling the linux kernel may be different, but benchmarks might be of interest. (I've found slight improvements with my single processor iBook (500 MHz/384 MB), but, of course, YMMV. Do note that running the infinately spawning variant (make -j), will eat ram until either the build is completed or vfork errors occur. _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
