[MacPorts] #20132: ghc missing variable definitions in 10.6

[MacPorts]

#20132: ghc missing variable definitions in 10.6
------------------------------+---------------------------------------------
 Reporter:  snc@…             |       Owner:  gwright@…           
     Type:  defect            |      Status:  assigned            
 Priority:  Normal            |   Milestone:                      
Component:  ports             |     Version:  1.8.0               
 Keywords:  snowleopard       |        Port:  ghc                 
------------------------------+---------------------------------------------

Comment(by gwright@…):

 >
 > I think there is a miscommunication going on.
 >
 > The idea is to have 32 bit functionality be in the main ghc port. It
 would be an exclusive choice. Either ghc is 32 bit or it's 64 bit. The ghc
 port would read the build_arch variable and act accordingly. The resulting
 compiler would (only) produce 32 bit or 64 bit binaries.
 >
 > Maybe there is a detail of the ghc bootstrapping that I'm not
 understanding (or I simply misread the comments on this ticket). Still, a
 user should not have to install a different port.
 >
 > Please note: there are many of us who use Snow Leopard on 32-bit
 architectures. For instance, I have a MacBook Pro with a Core Duo
 processor. It would be nice to be able to simply "sudo port install ghc".
 >

 The user will get a ghc the runs natively on his or her machine.  What I'm
 wrestling with is how to provide a mechanism to produce universal
 binaries.  Since the ghc compiler itself can only produce one kind binary,
 we need two compilers to do this (and you need to be running 64 bit Snow
 Leopard).  As mentioned one of the previous comments, if you avoid GUI
 libraries and bundle up an app with the appropriate 64 bit libraries, you
 can run 64 bit code on a 32 bit platform.  But this constraint is too
 stringent for general use.

 With two compilers, at least it will be possible to build a universal
 binary. This is just the bare mechanism; the haskell ports in MacPorts
 won't be able to be built universal for a while.

 > It sounds like you are trying to solve a harder problem than necessary.
 Getting the ghc port working at all looks like difficult task. I think
 installing one "flavor" of ghc is sufficient. Maybe that's naïve of me.

 As of this morning, I can build both 32 and 64 bit versions on Snow
 Leopard.  The average user will get the correct ghc automatically. The
 hard part has always been making everything "just work" and hide the
 infelicities of the ghc build system.

-- 
Ticket URL: <http://trac.macports.org/ticket/20132#comment:109>
MacPorts <http://www.macports.org/>
Ports system for Mac OS