Gnu Operating System For Mac

  1. Gnu Operating System Download
  2. Linux Operating System
  3. Gnu Linux Operating System

Download GNU Make for Mac - Open source and command line based utility designed to help developers build, configure, install and uninstall programs from their source files SOFTPEDIA® Windows. GNU Emacs For Mac OS X Pure builds of Emacs for Mac OS X.

[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

Emacs and the Mac OS. Emacs built on the Mac OS supports many of its major features: multiple frames, colors, scroll bars, menu bars, use of the mouse, fontsets, international characters, input methods, coding systems, and synchronous subprocesses (call-process).Much of this works in the same way as on other platforms and is therefore documented in the rest of this manual. This contains current versions (4.7 is the stable release) of gfortran (free, open source, GNU Fortran 95 compiler), gcc (GNU C) and g (GNU C) compilers that can perform auto-vectorization (i.e. Modify code to take advantage of AltiVec/SSE, automatically) and other sophisticated optimizations like.

Emacs built on the Mac OS supports many of its major features:multiple frames, colors, scroll bars, menu bars, use of the mouse,fontsets, international characters, input methods, coding systems, andsynchronous subprocesses (call-process). Much of this works inthe same way as on other platforms and is therefore documented in therest of this manual. This section describes the peculiarities of usingEmacs under the Mac OS.

The following features of Emacs are not yet supported on the Mac:unexec (dump-emacs), asynchronous subprocesses(start-process), and networking (open-network-stream).As a result, packages such as Gnus, GUD, and Comint do not work.

Since external programs to handle commands such asprint-buffer and diff are not available on the Mac OS,they are not supported in the Mac OS version.

AG.1 Keyboard Input on the MacKeyboard input on the Mac.
AG.2 International Character Set Support on the MacInternational character sets on the Mac.
AG.3 Environment Variables and Command Line Arguments.Setting environment variables for Emacs.
AG.4 Volumes and Directories on the MacVolumes and directories on the Mac.
AG.5 Specifying Fonts on the MacSpecifying fonts on the Mac.
AG.6 Mac-Specific Lisp FunctionsMac-specific Lisp functions.
[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

AG.1 Keyboard Input on the Mac

On the Mac, Emacs can use either the option key or thecommand key as the META key. If the value of the variablemac-command-key-is-meta is non-nil (its default value),Emacs uses the command key as the META key. Otherwise ituses the option key as the META key.

Most people should want to use the command key as the META key,so that dead-key processing with the option key will still work. This isuseful for entering non-ASCII Latin characters directly from the Mackeyboard, for example.

Gnu Operating System Download

Emacs recognizes the setting in the Keyboard control panel andsupports international and alternative keyboard layouts (e.g., Dvorak).Selecting one of the layouts from the keyboard layout pull-down menuwill affect how the keys typed on the keyboard are interpreted.

The Mac OS intercepts and handles certain key combinations (e.g.,command-SPC for switching input languages). These will notbe passed to Emacs.

The Mac keyboard ordinarily generates characters in the Mac Romanencoding. To use it for entering ISO Latin-1 characters directly, setthe value of the variable mac-keyboard-text-encoding tokTextEncodingISOLatin1. Note that not all Mac Roman charactersthat can be entered at the keyboard can be converted to ISO Latin-1characters.

To enter ISO Latin-2 characters directly from the Mac keyboard, setthe value of mac-keyboard-text-encoding tokTextEncodingISOLatin2. Then let Emacs know that the keyboardgenerates Latin-2 codes, by typing C-x RET k iso-latin-2RET. To make this setting permanent, put this in your`.emacs' init file:

[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

AG.2 International Character Set Support on the Mac

The Mac uses a non-standard encoding for the upper 128 single-bytecharacters. It also deviates from the ISO 2022 standard by usingcharacter codes in the range 128-159. The coding systemmac-roman is used to represent this Mac encoding. It is usedfor editing files stored in this native encoding, and for displayingfile names in Dired mode.

Any native (non-symbol) Mac font can be used to correctly displaycharacters in the mac-roman coding system.

The fontset fontset-mac is created automatically when Emacsis run on the Mac. It displays characters in the mac-romancoding system using 12-point Monaco.

To insert characters directly in the mac-roman coding system,type C-x RET k mac-roman RET, customize the optionkeyboard-coding-system, or put this in your init file:

This is useful for editing documents in native Mac encoding.

You can use input methods provided either by LEIM (see section Q.4 Input Methods) or the Mac OS to enter international characters.

To use the former, see the International Character Set Support sectionof the manual (see section Q. International Character Set Support).

To use input methods provided by the Mac OS, set the keyboard codingsystem accordingly using the C-x RET k command(set-keyboard-coding-system). For example, for TraditionalChinese, use `chinese-big5' as keyboard coding system; forJapanese, use `sjis', etc. Then select the desired input method inthe keyboard layout pull-down menu.

The Mac clipboard and the Emacs kill ring (see section H.7 Deletion and Killing) areconnected as follows: the most recent kill is copied to the clipboardwhen Emacs is suspended and the contents of the clipboard is insertedinto the kill ring when Emacs resumes. The result is that you can yanka piece of text and paste it into another Mac application, or cut or copyone in another Mac application and yank it into a Emacs buffer.

The encoding of text selections must be specified using the commandsC-x RET x (set-selection-coding-system) or C-xRET X (set-next-selection-coding-system) (e.g., forTraditional Chinese, use `chinese-big5-mac' and for Japanese,`sjis-mac'). See section Q.9 Specifying a Coding System, for more details.

[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

AG.3 Environment Variables and Command Line Arguments.

Environment variables and command line arguments for Emacs can be setby modifying the `STR#' resources 128 and 129, respectively. A commonenvironment variable that one may want to set is `HOME'.

The way to set an environment variable is by adding a string of theform

to resource `STR#' number 128 using ResEdit. To set up theprogram to use unibyte characters exclusively, for example, add thestring

[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

AG.4 Volumes and Directories on the Mac

The directory structure in the Mac OS is seen by Emacs as

Gnu operating system for mac download

Linux Operating System

So when Emacs requests a file name, doing file name completion on`/' will display all volumes on the system. You can use `..'to go up a directory level.

To access files and folders on the desktop, look in the folder`Desktop Folder' in your boot volume (this folder is usuallyinvisible in the Mac Finder).

Emacs creates the Mac folder `:Preferences:Emacs:' in the`System Folder' and uses it as the temporary directory. Emacsmaps the directory name `/tmp/' to that. Therefore itis best to avoid naming a volume `tmp'. If everything workscorrectly, the program should leave no files in it when it exits. Youshould be able to set the environment variable TMPDIR to useanother directory but this folder will still be created.

[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

AG.5 Specifying Fonts on the Mac

Gnu Linux Operating System

It is rare that you need to specify a font name in Emacs; usuallyyou specify face attributes instead. But when you do need to specifya font name in Emacs on the Mac, use a standard X font name:

See section AE.7 Font Specification Options. Wildcards are supported as they are on X.

Native Apple fonts in Mac Roman encoding has maker name appleand charset mac-roman. For example 12-point Monaco can bespecified by the name `-apple-monaco-*-12-*-mac-roman'.

Native Apple Traditional Chinese, Simplified Chinese, Japanese, andKorean fonts have charsets `big5-0', `gb2312.1980-0',`jisx0208.1983-sjis', and `ksc5601.1989-0', respectively.

Single-byte fonts converted from GNU fonts in BDF format, which are notin the Mac Roman encoding, have foundry, family, and character setsencoded in the names of their font suitcases. E.g., the font suitcase`ETL-Fixed-ISO8859-1' contains fonts which can be referred to bythe name `-ETL-fixed-*-iso8859-1'.

[ < ][ > ][ << ][ Up ][ >> ][Top][Contents][Index][ ? ]

AG.6 Mac-Specific Lisp Functions

The function do-applescript takes a string argument,executes it as an AppleScript command, and returns the result as astring.

The function mac-file-name-to-posix takes a Mac file name andreturns the GNU or Unix equivalent. The functionposix-file-name-to-mac performs the opposite conversion. Theyare useful for constructing AppleScript commands to be passed todo-applescript.

[ << ][ >> ][Top][Contents][Index][ ? ]

This document was generatedon April 2, 2002using texi2htmlSkip to end of metadataGo to start of metadata

After installing the GNU compilers, you may want to check out the HOWTO for installing Open MPI on Mac OS X.

This HOWTO will guide you through the installation of the GNU C, C++ and Fortran compilers 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.

Requirements

To install the GNU compilers as described in this HOWTO, you'll need the following:

  • 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)
Linux

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.

  • 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 .bashrc file rather than the .bash_profile file. To confirm, do the following:
    • Open a new terminal window using your terminal emulator of choice. This will reread the either the .bash_profile file or the .bashrc. If the new gcc version is not returned when typing

      then your terminal emulator may be reading the .bashrc file.

    • You can fix this one of two ways
      • Create a symbolic link called .bashrc that points to .bash_profile by typing

      • Modify the order of directories that are searched for commands by typing

Related