Mac
Thanks Walter Roberson! I manage to install the C & Fortran compiler in mac (OS10.13) with Matlab 2016b. Mex -setup fortran works. But when I run a code from a project gives me a issue which is listed on your post. Undefined symbols for architecture x8664: 'mxsetfield', referenced from: mexfunction in xxx.o. Mac; iPad; iPhone; Watch; TV; Music; Support; Shopping Bag + Cancel Apple ID. Open menu Close menu. Sign In; FAQ; Having trouble signing in? Enter your Apple ID to.
This post shows how to add an entry to the Mac OS X PATH variable – for the current terminal session only, permanently for the current user only and permanently for all users on a Mac OS X system.
In this example, the Tomcat startup.sh executable is added to the Mac OS X Path Variable so that is can be run from the terminal without having to use the full path name.

Summary

  1. Add Entry to Mac OS X PATH Variable – Current Terminal Session Only
  2. Add Permanent Entry to Mac OS X PATH Variable – Current User Only
  3. Add Permanent Entry to Mac OS X PATH Variable – All Users on the System (Global)

1 Add Entry to Mac OS X PATH Variable – Current Terminal Session Only

  • Open a new terminal window and use the echo command to view the PATH variable.
  • By default, the variable should be set to something like this on Mac OS X Sierra (here 10.12.5):
  • On my system, the Tomcat home is located at /Applications/apache-tomcat-9.0.0.M17
  • Staring the server using the startup.sh, requires using the full path name, otherwise it is not found.

Ifort Mcmodel

  • To add the Tomcat bin folder to the PATH variable for the current terminal session only, execute:
  • Use echo again to confirm the new entry to PATH:
  • For the current terminal session, the script startup.sh can now be executed from any location.
  • This PATH entry will be lost when closing the current terminal and is not available in a new terminal.

2 Add Permanent Entry to Mac OS X PATH Variable – Current User Only

  • To permanently add a PATH entry for the current user, navigate to the home folder:
  • And execute the below command to edit the user’s bash profile. Bash is the default shell on Mac OS.
  • Add the desired PATH entry with e.g. GNU nano as shown below. Use CTRL+O to save changes and CTRL+X to exit.
  • For the changes to take effect, close the current terminal window and open a new one.
  • Use echo $PATH again to confirm the entry was added.
  • Whenever a terminal is opened by the current user, the bash profile will add the specified PATH entry.

3 Add Permanent Entry to Mac OS X PATH Variable – All Users on the System (Global)

  • To permanently add a PATH entry for all users on Mac OS (global), the /etc/paths file is used.
  • Open the file for editing by running:
  • Add the desired PATH entry as shown below. This file maintains a list of PATH entries, one per row:
  • Use CTRL+O to save changes and CTRL+X to exit.
  • Switch to another user on the Mac and confirm that the PATH entry is present.
  • Note: Here, the user edgar will only be able to actually run the Tomcat startup.sh if the permissions have been set correctly by the user that owns the files. See chmod for setting permissions.
  • If read and execute permissions have not been set, errors indicating that the file was not found and other permission errors will occur.
  • Please register to leave a comment if you know additional or better approaches.

The command to invoke the compiler is ifort.

Note

For Windows and Mac OS* X systems, you can also use the compiler from within the integrated development environment.

Requirements Before Using the Command Line

On Linux* and Mac OS* X operating systems, you need to set some environment variables to specify locations for the various components prior to using the command line. The Intel Fortran Compiler installation includes a shell script that you can run in your terminal window to set environment variables. For more information, see Using the compilervars File to Specify Location of Components.

On Windows* operating systems, you typically do not need to set any environment variables prior to using the command line. Each of the Intel® Fortran Compiler variations has its own Intel Compiler command-line window, available from the Intel Fortran program folder. This window has the appropriate environment variables already set for the command-line environment.

Using the ifort Command from the Command Line

Use the ifort command either on a command line or in a makefile to invoke the Intel Fortran compiler. The syntax is:

For a complete listing of compiler options, see the Compiler Options reference.

You can either compile and link your projects in one step with the ifort command, or compile them with ifort and then link them as a separate step.

In most cases, you will use a single ifort command to invoke the compiler and linker.

The ifort command invokes a driver program that is the actual user interface to the compiler and linker. It accepts a list of command options and file names and directs processing for each file.

The driver program does the following:

You can also use ld (Linux OS and Mac OS X) or link (Windows OS) to build libraries of object modules. These commands provide syntax instructions at the command line if you request it with the /? or /help option.

Theifort command automatically references the appropriate Intel Fortran Run-Time Libraries when it invokes the linker. Therefore, to link one or more object files created by the Intel Fortran compiler, you should use the ifort command instead of the link command.

Because the driver calls other software components, error messages may be returned by these other components. For instance, the linker may return a message if it cannot resolve a global reference. The -watch (Linux OS and Mac OS X) or /watch (Windows OS) command-line option can help clarify which component is generating the error.

Note

Windows systems support characters in Unicode* (multibyte) format; the compiler will process file names containing Unicode* characters.

Syntax Rules

The following rules apply when specifying ifort on the command line:

Examples of the ifort Command

The following command compiles x.for, links, and creates an executable file. This command generates a temporary object file, which is deleted after linking:

Ifort

The following command compiles x.for and generates the object file x.o (Linux OS and Mac OS X) or x.obj (Windows OS). The c option prevents linking (it does not link the object file into an executable file):

The following command links x.o or x.obj into an executable file. This command automatically links with the default Intel Fortran libraries:

The following command compiles a.for, b.for, and c.for. It creates three temporary object files, then links the object files into an executable file named a.out (on Linux OS and Mac OS X) or a.exe (Windows OS):

When you use modules and compile multiple files, compile the source files that define modules before the files that reference the modules (in USE statements).

When you use a single ifort command, the order in which files are placed on the command line is significant. For example, if the free-form source file moddef.f90 defines the modules referenced by the file projmain.f90, use the following command:

To specify a particular name for the executable file, specify the -o (Linux* OS and Mac OS* X) or /exe (Windows* OS) option:

To redirect output to a file and then display the program output (Linux* OS and Mac OS X):

To place standard output into file one.out and standard error into file two.out (Windows* OS):

Or

To place standard output and standard error into a single file both.out (Windows OS):

Or

Other Methods for using the Command Line Window to Invoke the Compiler

You can use the command-line window to invoke the Intel Fortran Compiler in a number of ways, detailed below.

Using makefiles from the Command Line

Use makefiles to specify a number of files with various paths and to save this information for multiple compilations. For more information on using makefiles, see Using Makefiles to Compile Your Application.

Using the devenv command from the Command Line (Windows only)

Use devenv to set various options for the integrated development environment (IDE) as well as build, clean, and debug projects from the command line. For more information on the devenv command, see the devenv description in the Microsoft Visual Studio* documentation.

Ifort Mac Os

Using a .bat file from the Command Line

Use a .bat file to consistently execute the compiler with a desired set of options. This spares you retyping the command each time you need to recompile.