Hugs Mac OS
EchoHam classic is an upgraded version of the EchoMac first published in 2003 by Steve Palm (N9YTY), the only application dedicated to providing Echolink access via a native OS X application. Whilst there are no additional (external) features in this version, it has been re-coded to support the modern versions of OS X which make use of the. For purely nostalgic reasons, I finally got a version of Hugs98 to build (on Mac OS). I will be putting it up on GitHub for the curious. However, I do not recommend that anyone use Hugs98. The day GHCi came out way back when, I no longer had a good reason to use Hugs98.
| Downloading Hugs |
This is the September 2006 release of Hugs, a bugfix for the May 2006 release, and with libraries roughly matching the forthcoming GHC 6.6 release.
Note: the following modules are gone:
- Text.Regex: moved out of the base package and replaced with a new version that uses too much type class overlapping for Hugs.
- Data.FiniteMap: obsolete.
Packaged distributions for specific systems
Each of these packages installs Hugs using the native packaging system. If you want to run Hugs without installing it, build it from a source distribution (see below).
The Windows installer was prepared by Neil Mitchell, and includes the graphical interface WinHugs. Choose either:
WinHugs-Sep2006.exe (14 MB): WinHugs, other programs, and a large collection of libraries.
MinHugs-Sep2006.exe (1.4 MB) WinHugs and a minimal collection of libraries.
Modular packages for 12 architectures prepared by Arjan Oosting are in the Debian testing distribution.
Packages for i386, x86_64 and ppc (with extra libraries packaged separately, all maintained by Gérard Milmeister) are included in Fedora Extras.
x86 binary (3.4 MB), x86_64 binary (3.7 MB) and source (5.3 MB) RPMs for openSUSE 10.1 have been contributed by Sven Panne. These packages include the full set of libraries. Note that foreign import wrapper does not yet work in Hugs on x86_64, so if you need that you might try the x86 version instead.
A fresh port (including a full set of libraries) has been contributed by Oliver Braun.
A port is available on Mac Ports.
Packages for other systems will be listed here as they become available. In the meantime, you might like to try the March 2005 release.
Source distributions
Choose either:
Interpreter and a large collection of library packages: hugs98-plus-Sep2006.tar.gz (5.3 MB).
Interpreter and essential library packages: hugs98-Sep2006.tar.gz (2.1 MB), with other libraries available as separate Cabal packages.
The command to build is just `make' in the top-level directory. (For options, see the file `docs/building/unix.txt' included in the bundle.) Note also:
Some of the library packages are built only if the system you're building on is set up for compilation with certain C libraries. In particular you get the Haskell X11 and HGL packages only if X11 libraries are present, and the OpenGL, GLUT, OpenAL and ALUT packages only if the corresponding C libraries are available.
To build the Cabal packages, you'll need cpphs and hsc2hs. For the former, you can use either the cpphs-hugs installed with Hugs or a cpphs compiled with some Haskell compiler. For the latter, only hschs-hugs will do: the version installed by GHC produces GHC-specific output.
| Reporting bugs |
To report a bug in this version of Hugs, please either use the bug tracking system on the Hugs development page or send a message to hugs-bugs@haskell.org.
To ask a question about using Hugs, please send a message to hugs-users@haskell.org.
To ask a question about Haskell, please check the Haskell web site at haskell.org for further details, or send your message to haskell-cafe@haskell.org.
Please do not send direct mail to the authors or maintainers of Hugs if one of the above addresses would be more appropriate. We do read these mailing lists --- but so do many other people, who might be able to give you more appropriate or timely advice than us!
The Hugs 98 system is Copyright © Mark P Jones, Alastair Reid, the Yale Haskell Group, and the OGI School of Science & Engineering at OHSU, 1994-2004, All rights reserved. It is distributed as free software under a BSD-style license, which is included in the distribution in the file 'License'.
Skip to end of metadataGo to start of metadataAfter installing the GNU compilers, you may want to check out the HOWTO for installing Open MPI on Mac OS X.
Background
One of the nice things about Mac OS X is that you have a polished user interface atop a Unix operating system. This means that using command line utilities such as compilers is straightforward, making coding on your Mac easy. If you have a multi-core Mac (most should by now) and would like to run codes that use MPI to distribute processing across multiple processor cores, you should also check out the HOWTO for installing Open MPI on Mac OS X. Note that you'll need to follow the instructions on this page prior to installing Open MPI if you don't already have some set of compilers installed.
Hugs Mask
Requirements
To install the GNU compilers as described in this HOWTO, you'll need the following:
Hughes Macon
- A Mac running 10.11 (El Capitan)
- If you are using Mac OS X 10.6 - 10.10, check out the instructions for older versions of Mac OS X
- An Apple App Store account
- Internet access
Video instructions for Mac OS 10.11 (El Capitan) with Xcode 7
Rough video transcript:
Hello, and welcome to this screencast on how to install the GNU C, C++ and Fortran compilers for Mac OS 10.11 (El Capitan). In this video, I will show you how to install the compilers as well as Apple’s Xcode software, which is required for the compiler installation. For this video, I am assuming you are using a Mac running Mac OS 10.11, also known as El Capitan, that you have an Apple App Store account and that you have internet access. I am also assuming you have administrator access on your Mac, allowing you to install software. If you’re running an older version of Mac OS X, the installation procedure will be similar, but you can check out the link at the end of this video for the installation procedure on older versions of Mac OS X back to 10.6.
Step 1: We’ll begin by installing the current version of Apple’s Xcode software, Xcode 7. To install Xcode, start by opening the App Store app by clicking on the Apple logo on the top left of the menu bar and then selecting App Store… Once the App Store app opens, enter 'Xcode' into the search and press Enter. You can now click install to install Xcode. You may be prompted to enter your Apple ID and password if you’ve not previously installed applications via the App Store. Xcode is a pretty big download, so depending on the speed of your internet connection it may take some time to download and install. I’ll be back once the install is complete.
Step 2: Xcode has been downloaded and installed, and now we can move on to a critical second step for the Xcode install, installing the command line tools. To do this, we can use Spotlight to open the Terminal app. If you’re installing compilers, I am going to assume you’re at least somewhat familiar with using a terminal emulator. If not, you should still be able to do the install by following these instructions carefully. Once Terminal has opened, type in xcode-select --install. This will install the command line tools for Xcode, and you will be asked to perform the install using the typical application installation process. This may include asking you for your password.
Step 3: Now that Xcode is fully installed, we can move on to downloading the GNU compilers from the High-Performance Computing for Mac OS X website. The easiest way to get there is to open a web browser, Safari in this case. And type in 'High-performance computing Mac OS X' in the Google search. It should be the top hit. On that page, we’ll grab the latest STABLE version of the GCC compiler package and click the link to download.
Step 4: After the compilers have downloaded, we can return to the Terminal and navigate to the Downloads directory. We’ll install the compilers now using the `sudo` command, and before we do so, I’m going to give you a little warning. Using the sudo command can do major damage to your computer if you aren’t careful, so please type the following exactly as shown to do the install: sudo tar -xvf gcc-5.3-bin.tar -C /. If your downloaded package ends in .tar.gz, you’ll need to add z to the list of flags after the tar command. This should take just a moment and will install the compilers in /usr/local.
Step 5: Now the compilers are installed, and if you’re running Mac OS 10.11, you should be able to test the installation by typing gcc -v. It should show version 5.3. You can try the same with the Fortran compiler by typing gfortran -v. If they return the compiler versions as expected, you’re all set. Enjoy.
- If your compilers are not installed, you may need to add the installation location to the PATH environment variable, which tells the computer where to look for command line programs.
- In that case, the easiest thing to do is go to the installation HOWTO at the link at the end of this video and check out the last section of the instructions for the installation for Mac OS 10.9 or 10.10. There are some additional instructions that may help resolve your issues. If you’re still having trouble, double check you’ve followed the instructions exactly as given in the video and feel free to add a comment if you still need some help.
- OK, so that’s it. Thank you for watching. If you have any comments, please leave them below. In case you’re interested, here’s another link to a video on how to install the Open MPI software for running multi-core applications on your Mac using MPI, the message-passing interface. Good luck!
Instructions for older versions of Mac OS X (10.6 - 10.10)
Instructions for installing the GNU compilers for older versions of Mac OS X (10.6 - 10.10) have been moved and are available on another page.
Tips & Warnings
I mention all but the last of these tips and warnings in the text above, but it doesn't hurt to list them a second time...
- Beware that using sudo can do major damage to your computer if you aren't careful.
- Note that after installing Xcode, you also need to perform a critical additional step.
- Launch Xcode and install any available updates. Quit Xcode.
- Launch Terminal.app (in
/Applications/Utilities, hopefully you know that) Install the Command Line Tools for OS X by typing
This will open a dialog box to install the Command Line Tools for Xcode package. Install following the standard procedure.
- Launch Xcode and install any available updates. Quit Xcode.
- If the correct version of gcc is not being found at the command line after installation, it is possible that you're using a terminal emulator that reads the
.bashrcfile rather than the.bash_profilefile. To confirm, do the following:Open a new terminal window using your terminal emulator of choice. This will reread the either the
.bash_profilefile or the.bashrc. If the new gcc version is not returned when typingthen your terminal emulator may be reading the
.bashrcfile.- You can fix this one of two ways
Create a symbolic link called
.bashrcthat points to.bash_profileby typingModify the order of directories that are searched for commands by typing
Related
Hugs Mac OS