ghc-devel for darwinports
Hi, Due to overwhelming popular demand (well, Sven asked), darwinports now includes a port 'lang/ghc-devel', which builds from the head of the cvs. The default build includes support for openGL, so this is a way to get the latest OpenGL support for ghc, which now supports almost all of version 1.5. The ghc-devel port installs as ghc-6.3. (All of the executables have the "-6.3" suffix, so you can install ghc and ghc-devel without conflict. You invoke the new compiler as ghc-6.3 and the interactive environment as ghci-6.3.) ghc-devel depends on ghc, alex and happy, so if you have none of these installed and say sudo port install ghc-devel you'll get a full bootstrap build of the released version of ghc, along with builds of alex and happy (the lexer and parser generators, respectively), followed by a build of ghc from cvs. This may take some time (about 10 hours on an 800 MHz G4), but what would you rather have your CPU doing? Best Wishes, Greg Gregory Wright Antiope Associates LLC gwright@antiope.com
Do we have enough Haskell now for it to have it's own category? Python and other languages have their own category and it makes it easier for folks like me to "browse the haskell library" of darwinports. That is unless we can get some kind of decent query system in Darwinports for finding out what's available. I think a good enough query system would make most categories somewhat superfluous. dave On May 20, 2004, at 9:05 AM, Gregory Wright wrote:
Hi,
Due to overwhelming popular demand (well, Sven asked), darwinports now includes a port 'lang/ghc-devel', which builds from the head of the cvs. The default build includes support for openGL, so this is a way to get the latest OpenGL support for ghc, which now supports almost all of version 1.5.
The ghc-devel port installs as ghc-6.3. (All of the executables have the "-6.3" suffix, so you can install ghc and ghc-devel without conflict. You invoke the new compiler as ghc-6.3 and the interactive environment as ghci-6.3.)
ghc-devel depends on ghc, alex and happy, so if you have none of these installed and say
sudo port install ghc-devel
you'll get a full bootstrap build of the released version of ghc, along with builds of alex and happy (the lexer and parser generators, respectively), followed by a build of ghc from cvs. This may take some time (about 10 hours on an 800 MHz G4), but what would you rather have your CPU doing?
Best Wishes, Greg
Gregory Wright Antiope Associates LLC gwright@antiope.com
_______________________________________________ Darwinports mailing list Darwinports@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinports
This is a good idea. Maybe the infrastructure can support a haskell directory under lang/ where all of the haskell ports could reside. The existing arrangement is modeled on FreeBSD's port layout, which is a relatively flat hierarchy. This, I think, was caused by the limitations of using makefiles. Darwinports is driven by tcl scripts so in principle there is no reason not to organize the port tree as a deeper hierarchy. This would especially help the perl/python/gtk maintainers, as the number of supported versions grows. BTW, sometime soon I'll put together a haskell toolkit meta-port, which will build ghc, alex, haddock, buddha, c2hs, hat and anything else that people want. The idea is to have a consistent set of versions, so you can start a build in the evening and have a consistent, working ghc development environment ready to use by the time you enjoy a cup of coffee the next morning. Greg On May 20, 2004, at 5:22 PM, David Leimbach wrote:
Do we have enough Haskell now for it to have it's own category?
Python and other languages have their own category and it makes it easier for folks like me to "browse the haskell library" of darwinports.
That is unless we can get some kind of decent query system in Darwinports for finding out what's available. I think a good enough query system would make most categories somewhat superfluous.
dave
participants (2)
-
David Leimbach -
Gregory Wright