Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Multi-Processing Builds on Multiple CPUs

IP.com Disclosure Number: IPCOM000104284D
Original Publication Date: 1993-Mar-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 1 page(s) / 26K

Publishing Venue

IBM

Related People

Andrews Jr, R: AUTHOR

Abstract

The following is a description of a technique for distributing a large set of compiles (builds) on multiple CPU's.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Multi-Processing Builds on Multiple CPUs

      The following is a description of a technique for distributing
a large set of compiles (builds) on multiple CPU's.

      The solution consists of a "helper" program for make, the
program that drives the build process, that allows a standard make
process to run more than a single compile on more than a single CPU
at a time.  The program is called "mc," for "multiple compile."
Small modifications do need to be made to the Makefiles (the files
that drive the make processes) to make mc work.  These modifications
are easy to make, and can be easily disabled by using the macro
facility that make has when it parses its Makefiles.

      Mc works by sitting between make and the actual compilation
processes.  Make calls mc, and mc calls the compiler.  Mc fools make
into believing that the compile is done by immediately forking and
exiting.  Make is then free to decide what to compile next, and call
mc again, with different arguments.  The freshly spawned mc child
process can now start the compile.  If the compile is to be done on a
remote machine, rsh (a tcpip program to run a command on a remote
host) is used to migrate the compile.

Disclosed Anonymously.