Hi Danek, In recent review on my Erlang code, Roland Mainz asked why not generate 64bit binararies for Erlang/OTP:
http://www.opensolaris.org/jive/thread.jspa?threadID=58358&tstart=0 I investigated this a bit and finally figured out how to modify Erlang's build scripts for 64bit on Solaris(the main issue is how to use 64bit openssl library). However, I have a question now: where should I install those 64bits executable and libraries files? I had thought it should be /usr/bin/64 and /usr/lib/erlang/64, but there isn't /usr/bin/64. So, one possible solution is as following: - use /usr/lib/erlang/64 for erlang 64bit executables and libraries - use /usr/bin for symbol links to 64bit executables If so, however, 32bit binaries and 64bit binaries cannot co-exist on the same machine(or in the same proto area when building) because they share the common /usr/bin subdir. I wondered how other applications on SFW gate do this, so I looked at some: 1) postgres: it has it own root directory root directory: /usr/postgres/8.2 |- bin | +- 64 +- lib +- 64 2) flex: it installes 32bit executables only and places 64bit shared objects under /usr/lib/64. None of their appoaches can be borrowed for Erlang. :( How do you think the solution I proposed above? If we use that apporach, should fastrack document be modified too? BTW, I noticed many applications(for example, ruby) on SFW don't deliver 64bit binaries. I wonder what's the rule for that? (I guess this is not mandatory, right?) Thanks for any suggestions. Raymond
