Bug 83001

Summary: Erlang port is n/a for amd64
Product: Ports & Packages Reporter: Rasmus Kaj <kaj>
Component: Individual Port(s)Assignee: Jimmy Olgeni <olgeni>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
erlang.diff none

Description Rasmus Kaj 2005-07-05 10:40:07 UTC 
The erlang port (lang/erlang) is marked as  ONLY_FOR_ARCHS=i386.  I would like to add support for amd64.

If I do so (ONLY_FOR_ARCHS= i386 amd64), configure hangs at "checking for unreliable floating point execptions...".  Simply removing that test allows erlang to build and install on my amd64.

I'm told the reason for this behaviour is that floating point exceptions are precise on amd64, unlike most platform.  Linux then "fixes" this by stepping up the instruction pointer at floating point exceptions. The config test assumes this is done and hangs when it isn't.

In the long run, the test should probably be fixed rather than just avoided.

Fix: 

ONLY_FOR_ARCHS= i386 amd64 in the lang/erlang/Makefile, and remove the "checking for unreliable floating point execptions..." test.
How-To-Repeat: portinstall erlang
Comment 1 Pav Lucistnik freebsd_committer freebsd_triage 2005-07-05 22:17:23 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->olgeni

Over to maintainer.
Comment 2 Sam Lawrance freebsd_committer freebsd_triage 2005-12-20 06:51:54 UTC 
State Changed
From-To: open->feedback

Can you provide a patch for the port to do this?
Comment 3 Lapo Luchini 2006-01-19 11:37:00 UTC 
I made the following patch basing on reporter's suggestion.
I know nothing about erlang, but it compiled until the end and ejabberd
seems quite happy to compile with it, so I guess it is for sure better
than a broken port, on amd64 ;-)
Comment 4 Jimmy Olgeni freebsd_committer freebsd_triage 2006-03-20 23:22:14 UTC 
State Changed
From-To: feedback->closed

The erlang port was fixed for amd64 with a modified patch.