compiler available for x86 ?.
Tue Oct 10 17:18:00 CEST 2000
There is always Stand Alone Erlang which has had experimental support for
some time. I've never played with it but there is something in
Maybe the OTP team are planning to turn this into supported code sometime
From: Luc Taesch [mailto:]
Sent: 8 October 2000 21:52
To: Sean Hinde
Subject: Re: compiler available for x86 ?.
Sean Hinde wrote:
I guess you are talking about Linux, in which case the normal R7B etc
release works fine. It doesn't do native code compilation but beam compiled
code is fast enough for most things.
Maybe I missed the point of your question?
sorry for being so imprecise.
yes, im interesting in distributing a binary only.
1) i wanna deploy 30 times the same application, on client servers, and i
dont wanna bother intalling erlang, or
2) i have access to a server i cant impose to have erlang installed (say
3) or i wanna build utilitaries, and i dont wanna be troubled with release
conflicts as time goes by.
4) a demo softwarein a rpm, and i dont want bothering people downloading 8
mo of environement, or they cant be root ( to install erlang)
these are different points where i may be interested to build a self
contained binary. so i was looking at how to do that.
and which constraints it may brings, like language restrictions.
(and yes, R7b is quick enough for me!)
> -----Original Message-----
> From: Luc Taesch [ mailto:
> Sent: 7 October 2000 12:35
> Subject: compiler available for x86 ?.
> i once asked which of compiler is available for x86.
> hipe is for sparc, and etos link is still un-available.
First, they ignore you.
Then, they laugh at you.
Then, they fight you.
Then, you win.
Working code is what matter, not your market capitalization.
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.
More information about the erlang-questions