First, let me say that the compile farm is fantastic!
I was able to clean up a few portability issues in
libEMF in less than 10 minutes on all of the Linux
and FreeBSD boxes.
However, I ran into a few problems on the Solaris
machine. First, "config.guess" from the latest
version of automake (1.5c) uses the "cc" command to
glean information about the platform. On the Solaris
machine, /usr/ucb/cc (and /opt/SUNWspro/bin/cc) seems
to hang forever. Perhaps it is waiting for a license?
Are Sun's compilers officially supported on the
compile farm system? (Anyway, I removed /usr/ucb from
my PATH and got by this problem.)
Next, I got this message from my configure script
(from autoconf 2.52):
checking whether the linker (/usr/ccs/bin/ld)
supports shared libraries...
Releases of GCC earlier than version 3.0 cannot
create self contained shared libraries on Solaris
introducing a dependency on libgcc.a. Therefore,
libtool is disabling
-no-undefined support, which will at least allow you
to build shared
libraries. However, you may find that when you link
into an application without using GCC, you have to
`gcc --print-libgcc-file-name` to the link command.
We urge you to
upgrade to a newer version of GCC. Another option is
to rebuild your
current GCC to use the GNU linker from GNU binutils
2.9.1 or newer.
While I didn't see this exact problem, when I
compiled libEMF as a shared object, my test codes
behaved incorrectly: namely, the constructors for
global variables in the shared library were not
invoked when the library was loaded. Do you have any
plans to upgrade the GNU compiler system on the
Solaris machine? (or maybe you can tell what I did
wrong? I'm trusting libtool to do the right thing: It
does include libgcc as mentioned in the configure