failure to build erlang on sparcv9 Solaris 10 with the system gcc

build output

cd lib && \
  ERL_TOP=/var/tmp/pkgbuild-0/erlang/sparcv9/erlang-otp-73b4221 PATH=/var/tmp/pkgbuild-0/erlang/sparcv9/erlang-otp-73b4221/bootstrap/bin:${PATH} \
        make opt SECONDARY_BOOTSTRAP=true
make[1]: Entering directory `/var/tmp/pkgbuild-0/erlang/sparcv9/erlang-otp-73b4221/lib'
make[2]: Entering directory `/var/tmp/pkgbuild-0/erlang/sparcv9/erlang-otp-73b4221/lib/hipe'
=== Entering application hipe
make[3]: Entering directory `/var/tmp/pkgbuild-0/erlang/sparcv9/erlang-otp-73b4221/lib/hipe/misc'
erlc -W  +debug_info +warn_exported_vars +warn_missing_spec +warn_untyped_record -o../ebin hipe_consttab.erl
make[3]: *** [../ebin/hipe_consttab.beam] Bus Error (core dumped)
make[3]: Leaving directory `/var/tmp/pkgbuild-0/erlang/sparcv9/erlang-otp-73b4221/lib/hipe/misc'

Looks like the executable name got truncated there:

 # file ./erlang-otp-73b4221/lib/hipe/misc/core
 ./erlang-otp-73b4221/lib/hipe/misc/core:        
       ELF 64-bit MSB core file SPARCV9 Version 1, from 'beam.smp'

I was hoping that this would be an "you're an idiot for trying to build it that way, do it this way instead" type of questions, but I'm not sure I'm going to be so lucky :-/

Some other system info that might be pertinent:

# isainfo -v
64-bit sparcv9 applications
        vis2 vis 
32-bit sparc applications
        vis2 vis v8plus div32 mul32 

# uname -a
SunOS ecbuild-20 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-280R

# gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
Configured with: /gates/sfw10/builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)

In case anyone is paying attention to this, I believe this is an issue with the gcc that ships with sparc solaris 10. Building a newer gcc is rather laborious process, but I'm working that angle.

I've opened a thread on stackoverflow for this, complete with the solution:

http://stackoverflow.com/questions/6561133/why-does-my-erlang-build-fail-with-a-core-dump-on-solaris-sparc/