make failure

[Per Hedeland]

Bob Smart <smart@REDACTED> wrote:
>Make fails on a farly generic solaris 2.5.1 machine with gcc:
>
>make[2]: Entering directory `/trout/projects/ssg3/otp_src_R6B-0/lib/mnesia_session'
>make[3]: Entering directory `/trout/projects/ssg3/otp_src_R6B-0/lib/mnesia_session/src'
>erlc -W  -pa /trout/projects/ssg3/otp_src_R6B-0/lib/mnesia_session/ebin -I ../include -I {error_logger,{{2000,7,21},{15,23,15}},'inet_parse:~p:~p:  Eshell V4.9.1  (abort with ^G) /trout/projects/ssg3/otp_src_R6B-0/bootstrap/lib/ic-3.8.1/include \|'\034']}
>+'{preproc_cmd, "gcc -x c++ -E -D_CORBA_"}' \
>+'{{impl, "mnesia_corba_session"}, "mnesia_session_impl"}' \
>mnesia_corba_session.idl
>/bin/sh: syntax error at line 1: `(' unexpected

That's weird, I've successfully built R6B-0 on Solaris 2.5.1 - well, at
least most of it, some parts failed because that system didn't have a
complete g++/libg++ installation, but as far as I recall the failure
wasn't like the above.

The strange "/bin/sh:" line is in my experience typical of trying to run
a binary from another architecture/OS (the shell tries to run it as a
script when exec() fails) - are you sure you started with a cleanly
unpacked distribution, and don't have non-Sun/Solaris stuff in e.g.
personal directories in your $PATH that might interfere?

In any case, you do need not only g++ (which comes "automatically" with
gcc unless you explicitly prevent it) but also the corresponding libg++
(which is a separate distribution - hm, I guess it's actually libstdc++
for modern versions of gcc/g++) in order to get everything to build, so
you might want to check this out.

--Per Hedeland
per@REDACTED