After sucessfully fixing the BSDs (see last journal entry), I was so foolish to tackle Solaris.
Needless to say, they never work. Maybe it is because the administrators of these machines are clueless, I don't know (but it's consistently the case everywhere: Sourceforge, the various CIP pools in my university, the chair of high-performance computing etc.).
Anyway, the first thing I observe is a broken terminal. There might be a
vi around, but it can't be used due to the screwed terminal.
On with compilers. This is where it becomes really ugly. The Solaris machines of sourceforge's compile-farm have two perls installed (5.6.1 which is a progress - usually they have 5.004_something at most, and 5.8.0). 5.6.1 was compiled with
cc. However, trying to compile my module didn't work as there is no
cc around anywhere. Setting
CC=gcc wont work out of the box either since the gcc wont know about some of cc's compiler flags. Alas, changing the Makefile is impossible without a working editor.
So I tried 5.8.0 which was in fact compiled with gcc. That didn't quite work either because neither
__srv4__ (note the extremely consistent naming scheme) are defined. I suppose those symbols are only defined when using suncc which I don't have.
In the meantime (I was trying a few things while writing this journal), I did find the
cc. It was hidden as
/usr/ucb/cc. But would it work? No:
bash-2.05$ perl Makefile.PL CC=/usr/ucb/cc
Writing Makefile for Device::CDROM
make: *** [CDROM.o] Error 1
Reason is that
/usr/ucb/cc is just a shell script calling the real cc which is - as you may have guessed - not installed.