Those are internal compiler phases invoked by the userland driver program (gcc, icc, etc) and aren't generally meant for separate use by the programmer.
(And the phases invoked vary from compiler to compiler and depend on which flags are used)

So, that fixed things?

Looks to me like you're trying to build openmpi with support for some feature that's not installed. Initial suggestion is to run an emerge --deep -a world, then revdep-rebuild (from gentoolkit) to see if the system detects something that should be pulled in.

Ah, GridEngine?

If you build your MPI with GE integration you can just say "mpirun <yourprogram>" at the end and the MPI will take care of all the hostfile and -np bits for you.

#nodes=5
#ncpu=`expr $nodes \* 2`

these are just comments as far as the shell executing the job is concerned and are ...

What is "mpirun -3 5 ..." supposed to do? Do you want 5 processes?

Are you sure it's something happening on wlan0 that is doing this? Maybe another network interface is responsible.

Yes, it builds.

"module" is to manage extra / different versions of packages, e.g. if you have extra compilers from various vendors, you can use module to add/remove PATH, MANPATH etc. settings.

"module" as in http://modules.sourceforge.net/

It sets an environment variable called MODULE_VERSION: this was being used by portage and was misdirecting the build to a non-existent directory.

* Package: perl-core/Encode-2.40-r1
* Repository: gentoo
* Maintainer: perl@gentoo.org
* USE: amd64 elibc_glibc kernel_linux multilib userland_GNU
* FEATURES: sandbox splitdebug
>>> Unpacking source...
>>> Unpacking Encode-2.40.tar.gz to /var/tmp/portage/perl-core/Encode-2.40-r1/work
>>> Source ...

Can you post the /etc/inittab? That might tell us what the runlevel message is about.

Oh, well my brain apparently failed today. I've never actually encountered that problem (in over 20 years )

"search" does the same thing as "domain" here, however search lets you list out multiple names, whereas domain is just a single value.

There's a man page for resolv.conf(5) that shows how this process works.

OpenMP directives/pragmas are not processed by gcc unless the -fopenmp option is given, as you noted (supported != always in play). You can use it on a system with any number of cores, but you'll only see potential speedups on multi-core systems: so, yes, a dual-core system can scale to 2 threads ...

error: expected '=', ',', ';', 'asm' or '__attribute__' before 'rlock'

Giveaway. Indicates a variable declaration with an unknown type. This probably means a missing #include, in this case, of <pthread.h> in that source file. Probably...

in .ssh/config you can add entries such as

Baffling.

Could there perhaps be a minor formatting error in /etc/group that is being ignored locally, but the YP make process is choking on?
How did you create/edit the local groups? groupadd/vigr and friends, or ... ?

is MERGE_GROUP=true in /var/yp/Makefile ?

also make sure MINGID is incorporating the groups you want visible to YP.

one thing to try is to force a group update: touch /etc/group and make in /var/yp

The build for the YP maps is in /var/yp on the YP/NIS server (presumably also the head node? or use "ypwhich" to find the server).

A "make" in there will incorporate local changes into YP/NIS. passwd and group should be handled by default.

> normal?

depends on your setup. From what you've said, I'm guessing that the YP group map has been set up but is empty, and that the group(s) you're expecting to see are only in /etc/group on the head (so the "files" repository on the head picks up the groups for you, but neither "files" nor "nis ...

can you "ypcat passwd" (and group) on both the head and compute nodes?

Check also that "getent passwd" (and group) delivers the concatenation of /etc/passwd(group) and the NIS map.

what's in nsswitch.conf on the compute nodes?

what's the group setting in /etc/nsswitch.conf?

warning: libcrypto.so.0.9.8, needed by /usr/lib/gcc/i686-pc-linux-gnu/4.4.4/../../../libldap.so, not found (try using -rpath or -rpath-link)

There you go. You're trying to build OpenSSH without OpenSSL. That's going to end in tears...

Do you have OpenSSL installed, and if so, which version ...

Looks like the badness happened right before the first line you included. Can you post the full build log for openssh?

Looks like you've accidentally got a carriage-return (Control/^M) on the end of the first line in /etc/init.d/net.lo