Use the CONCURRENCY_LEVEL environment variable eg make-kpkg kernel_image CONCURRENCY_LEVEL=4 after installing distcc into a masquerade directory.

REG) See the Kernel HOWTO for some information. Also, there are people at http://www.kernelnewbies.org/ who are usually willing to help. William Stearns) The Buildkernel script walks you through an entire kernel build, including downloading the necessary files, patching the source, building the kernel and modules, installing the lot into lilo, and optionally building pcmcia-cs, cipe, and freeswan code for that kernel.

Yes. Install libc5-altdev and altgcc packages (from the oldlibs section). You can find the appropriate libc5-compiled gcc and g++ in directory /usr/i486-linuxlibc1/bin. Put them in your $PATH variable to get make and other programs to execute these first.

In order to make sure that your system has been installed from the real Debian base disks check for the existence of /etc/debian_version file, which contains a single one-line entry giving the version number of the release, as defined by the package base-files.

Just like any other source package on Debian. First, as root, install the packages required to build Cernlib: apt-get install build-essential fakeroot Then, reverting to a normal user, cd into a working directory and download the Debianized Cernlib source: apt-get source cernlib If you want to add additional compiler flags to the build process, edit debian/rules and add them to the declaration of the LOCAL_DEFINES Make variable.

Like cdrecord, cdda2wav needs a sophisticated make program like Jörg Schilling's smake or GNU gmake. Pure posix make functionality is not enough.

REG) First make sure you have the latest version of that kernel series. Perhaps a pre-patch already has a fix. If not, search the list archives for a fix. Don't contribute to noise on the list by asking a question that may already have been answered. If the problem has not yet been fixed, try digging into the code yourself and post a fix to the mailing list.

In order for you to do any major work of any kind, you'll probably have to have the source and be able to do things with it. (Unless you just happen to be a super ResEdit/Macsbugs hacker that can play with the assembly. :) ) If you just want to test the things that others have done, you won't need to.

Compiling a kernel for the ARM architecture is very similar to any other architecture. Russell King maintains a document detailing the process.

Iptables can either be compiled into the kernel or as a modules, it does not really matter. If some of the modules are missing, then respective feature won't work and you will get an error trying to load generates script. For example, if you compile everything into the kernel and leave ipt_LOG module out, then logging will stop working and you will get errors trying to load rules with logging turned on.

Remember that when you apply a patch to the kernel, you must use the -p0 or -p1 option: otherwise, the patch may be misapplied. See the patch manual page for details. ld: unrecognized option -qmagic means that you should get a newer linker, from ftp://tsx-11.mit.edu/pub/linux/packages/GCC/, in the file binutils-2.8.1.0.1.bin.tar.gz.

This is a little more complicated since you won't have any Debian infrastructure tools. You will need the two files cernlib_2006.dfsg.2.orig.tar.gz and cernlib_2006.dfsg.2-2.diff.gz. Having downloaded these files to a working directory, run the following commands: gunzip -c cernlib_2006.dfsg.2.orig.tar.gz | tar xf - in question 2.

use: # make [modules|zImage|bzImages] MAKE="make -jX" where X=max number of processes. WARNING: This won't work for "make dep". With a 2.1.x like kernel, see also the file /usr/src/linux/Documentation/smp for specific instruction. BTW, since running multiple compilers allows a machine with sufficient memory to use use the otherwise wasted CPU time during I/O caused delays make MAKE="make -j 2" -j 2 actually even helps on uniprocessor boxes (from Ralf B?chle). In the 2.

Compile the kernel in the normal way (Follow the instructions in /usr/src/linux/README), but at the end, instead of make zImage or make zlilo, you should do # make vmlinux # make modules # make modules_install

Check for the existence of the file /var/lib/dpkg/status. This contains a stanza reporting the status of each of the installed Debian packages on a system.

The existence of the program dpkg shows that you should be able to install Debian packages on your system. In order to make sure that your system has been installed from the real Debian base disks check for the existence of /etc/debian_version.

The easiest way is to just shut down the distccd server. When it comes back up, clients will start using it again. If I set DISTCC_HOSTS="remote_host localhost" then the project seems to be compiled only on the remote host (I see traces in ethereal and compilation is slow). You are probably not using the -j option to make or scons, so it's only compiling one file at a time. Only the first host in the list will be used in this case.

All objects files were created , but when I issue command for execution as ./executable then program takes so much time as without distcc. Kindly tell me that how this execution time can be reduced. All things work Properly , But all processors of systems are not utilized during EXECUTION of programs. distcc makes building the program take less time. The program that is produced is the same as for a local build.

From: libes (Don Libes) To: wren@io.nosc.mil Subject: Compile fails with: Don't know how to make pty_.c > I'm trying to compile Expect on hpux 9.01, > downloaded from ftp.cme.nist.gov expect.tar > after running config > the make fails with "Don't know how to make pty_.c. (compile fails) > I see three versions pty_sgttyb.c, pty_termios.c and pty_unicos.c in > the load, but the configure picked none of them. > I tried forcing to pty_termios.

REG) Here are some basic guidelines for posting patches. For information on how to generate patches, see the entry by RRR below. Ensure the patch does not have trailing control-M characters on each line. A number of broken tools used to encode patches add control-M for "DOS compatibility". This breaks many versions of patch, so be sure to configure your tools properly, or use unbroken tools, otherwise your patch will be silently deleted. Include the patch inline in your email, in plain text.

enable "RTC support" (from Robert G. Brown). Note that inserting RTC support actually doesn't afaik prevent drift, but according to a discussion [Robert G. Brown] remember from a year ago or so it can prevent lockup when the clock is read at boot time. A note from Richard Jelinek says also that activating the Enhanced RTC is necessary to get the second CPU working (identified) on some original Intel Mainboards.

You are not using the new make buildkernel and make installkernel targets, and your source tree is different from the one used to build the currently running system (e.g., you are compiling 4.3-RELEASE on a 4.0-RELEASE system). If you are attempting an upgrade, please read the /usr/src/UPDATING file, paying particular attention to the ''COMMON ITEMS'' section at the end.

Please ensure this is not caused by using a broken toolchain, binutils or third party patch. A quick look at the Kautobuild for kernel you are trying to build should give some idea if the error is expected. Once all these things have been checked the issue should be reported to the community mailing list. When reporting these problems, always include as much information as possible as a minimum the full build line. This can be obtained by re-running the make with an additional argument: V=1

You will need the following tools in order to compile the kernel. Make sure they are in your path ahead of the SunOS versions. GNU make You can find these tools for Sun Solaris 2.3 and up at http://www.ibiblio.org/pub/solaris/sparc Please note that for the newer kernels you will need GCC version 2.7.x, or EGCS 1.0.3 and up. See also the GCC Home Page.

In order to produce a 64-bit kernel for an UltraSPARC based machine (sparc64), you will need an appropriate compiler and libraries. In this case that's egcs64, the Experimental GNU Compiler System for sparc64. If you are not using any distribution, the best thing to do next to build it from the sources (see the GCC homepage) is extract the 64-bit EGCS or GCC for sparc64from one. Jakub states, the 64-bit support in gcc is complicated: egcs64 (which is a snapshot of egcs 1.0.

There is a file, /etc/debian_version, which contains a single one-line entry giving the version number of the release, as defined by the package base. Users should be aware, however, that the Debian system consists of many parts, each of which can be updated (almost) independently. Each Debian "release" contains well defined and unchanging contents. Updates are separately available. For a one-line description of the installation status of package foo, use the command dpkg -l foo.