On 05/06/08, Danek Duvall wrote:
> Alan mentioned this a bit, but for completeness ...
Thank Danek and Alan for your reply.
> 64-bit libraries go into /usr/lib/$(MACH64), where MACH64 is amd64 on x86
> and sparcv9 on sparc. There's a "64" symlink pointing to the appropriate
> arch name on each platform, though most apps use the arch name directly,
> for whatever reason.
Yes, I will use $(MACH64), instead of "64" symlink. That also
works for /usr/bin.
> 64-bit executables are a bit different. Assuming that you want to
> automatically run the 64-bit executable on a 64-bit capable machine, then
> you need to put a special executable in /usr/bin which calls isaexec(),
> which in turn executes either amd64/foo or i386/foo. The memcached folks
> did this already for SFW, so you'd probably want to make that a more
> general thing in SFW.
I didn't consider to do that. I prefer to just place 64bit
executables under /usr/bin/${MACH64}, and let user to set
PATH to choose what they want to use.
> You'll also need to go back to the ARC and let them know what you're
> planning on doing. That can probably be handled as a simple update to the
> existing case.
>
> Now, that's all if you really want a 64-bit erlang. It's not at all clear
> to me that there'd be a whole lot of demand for it and I certainly don't
> see a compelling need for it, but it seems that the python and tcl folks
> went that route. Not ruby or perl.
Since this was asked and I have investiaged it, I will implement
it. I will update fasttrack as soon as I finish and test my code
and send the new version to you. Thanks.
Raymond
