[erlang-questions] How to compiler Erlang for the TILEPro64?

[Stefan Marr]

Hi Björn-Egil:

Thanks a lot, worked great!

Here some notes, about things I had "trouble" with.

The SKIP files seem to be deleted by the configure step, thus I had to recreate them afterwards. Otherwise I get linker errors, since the tile-gcc tried to link some IA32 files. Think it was complaining about crypto.a or something similar.

For the release step, I also had to do a "touch lib/mnesia/SKIP" for some reason, I haven't investigated further.

It is also good to know, that <release dir> has to be an absolute path :)

Afterwards, you can have a very happy helloworld with
tile-monitor --pci --here -- bin/erl -noshell -s hello_world start -s init stop
 

I have not yet looked anywhere into the actual support provided for the Tilera chips, but is there something like printing the core id the process is running on?
Are there any parameters to erl to specify how many hardware cores to use?
And, are there some benchmarks or examples which are using the tiles explicitly?

Thanks
Stefan



On 29 Jan 2010, at 15:45, Björn-Egil Dahlberg wrote:

> Hi Stefan,
> 
> To compile Erlang for Tilera you can do the following,
> 
> 1) Setup the Tilera Environment.
> For example for me it is:
> 
> export TILERA_ROOT=/ldisk/tilera/TileraMDE-2.0.1.78377/tilepro
> export PATH=$TILERA_ROOT/bin:$PATH
> 
> This is the cross compile environment supplied to you by Tilera Corp.
> 
> 2) Setup The Erlang Build Environment:
> 
> tar -zxvf otp_src_R13B03.tar.gz
> cd otp_src_R13B03
> export ERL_TOP=`pwd`
> eval `./otp_build env_cross
> $ERL_TOP/xcomp/erl-xcomp-TileraMDE2.0-tilepro.conf`
> 
> Crypto (and its dependencies) will not work so you need to SKIP those.
> 
> 3) Build Erlang/OTP
> touch lib/crypto/SKIP
> touch lib/ssl/SKIP
> touch lib/ssh/SKIP
> ./otp_build configure
> ./otp_build boot -a
> ./otp_build release -a <release dir>
> 
> 4) Start Erlang,
> 
> cd <release dir>
> ./Install `pwd`
> tile-monitor --pci --here -- bin/erl
> 
> Of course you would probably want to upload everything to the card, just
> like other applications you need to upload.
> 
> Contact Tilera Corp. for optimal settings and hardware configuration.
> 
> This should work on R13B03. However, from R13B04 this way will change
> and it will be better support cross compilation.
> 
> Regards,
> Björn-Egil
> Erlang/OTP
> 
> 
> Stefan Marr wrote:
>> Hi:
>> 
>> I have tried to compile Erlang (otp_src_R13B03) for the TILEPro64.
>> 
>> I was starting from the following bits of information:
>> http://www.erlang.org/cgi-bin/ezmlm-cgi/4/44766
>> http://www.trapexit.org/Cross_compiling
>> 
>> 
>> When I tried to execute: ./otp_build env_cross $ERL_TOP/xcomp/erl-xcomp-TileraMDE2.0-tilepro.conf
>> 
>> I got an error asking me to do a
>> "eval `./otp_build env_cross $ERL_TOP/xcomp/erl-xcomp-TileraMDE2.0-tilepro.conf`" instead, but this command didn't generate any output.
>> 
>> The wiki article on the other hand, asks me to choose a target "TARGET=mips-linux" and I am not sure where to find out the right target.
>> 
>> Would be great, if someone could point me at some documentation, or could give me advice on how to compile Erlang for the Tilera card.
>> 
>> Many thanks and best regards
>> Stefan
>> 
>> 
> 

-- 
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 3956
Fax:   +32 2 629 3525