[erlang-questions] Building Erlang with the Sun Studio compiler

Berger, Daniel Daniel.Berger@REDACTED
Tue Aug 21 19:01:06 CEST 2007

> -----Original Message-----
> From: Chris Curtis [mailto:Chris.Curtis@REDACTED] 
> Sent: Tuesday, August 21, 2007 8:42 AM
> To: Berger, Daniel; erlang-questions@REDACTED
> Subject: RE: [erlang-questions] Building Erlang with the Sun 
> Studio compiler
> > -----Original Message-----
> > From: erlang-questions-bounces@REDACTED [mailto:erlang-questions- 
> > bounces@REDACTED] On Behalf Of Berger, Daniel
> > Sent: Tuesday, August 21, 2007 10:09 AM
> > To: erlang-questions@REDACTED
> > Subject: [erlang-questions] Building Erlang with the Sun Studio
> compiler
> > 
> > Hi,
> > 
> > I tried to build Erlang on my Solaris 10/Sparc box with the 
> Sun Studio 
> > Compiler 12, but it appears that you must build using Erlang using 
> > gcc/gmake. I think I've seen a Solaris package out there, but I'd
> rather
> > build from source, since packages can take a while to catch up with
> the
> > latest release, and may not be configured with the options I want.
> > 
> > Are there GNU extensions that Erlang absolutely has to have? If not,
> is
> > there any chance we can alter the appropriate files so that it will 
> > build using other toolchains?
> > 
> > Or, is there a way to build with Sun's compiler that I've missed?
> > 
> > Regards,
> I haven't personally tried it (no SPARC here), but you might 
> want to check out GCCFSS... it's a GCC front end integrated 
> with the Sun Studio SPARC backend, so you get GCC build 
> compatibility with what looks like a big performance boost. 
> It's at http://cooltools.sunsource.net/gcc/.
> --chris

Thanks Chris, that definitely looks interesting.

However, I still think removing the GNU specific dependencies is a
better long term solution. People are going to want to build from source
with their own compilers on other platforms as well, e.g. MS VC++,
Borland, the HP-UX compiler, etc.



This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.

More information about the erlang-questions mailing list