## 22.4 Installing Maple™ 

***Contributed by Aaron Kaplan. ******Thanks to Robert Getschmann. ***

 **Maple™**  is a commercial mathematics program similar to  **Mathematica®** . You must purchase this software from http://www.maplesoft.com/ and then register there for a license file. To install this software on DragonFly, please follow these simple steps.

 **Warning:** This description applies to FreeBSD, for which it was originally written. This may or may not apply to DragonFly at this point; while FreeBSD 4.x features usually translate over to DragonFly well, your mileage may vary.

  1. Execute the `INSTALL` shell script from the product distribution. Choose the ***RedHat*** option when prompted by the installation program. A typical installation directory might be `/usr/local/maple`.
  1. If you have not done so, order a license for  **Maple**  from Maple Waterloo Software (http://register.maplesoft.com/) and copy it to `/usr/local/maple/license/license.dat`.
  1. Install the  **FLEXlm**  license manager by running the `INSTALL_LIC` install shell script that comes with  **Maple** . Specify the primary hostname for your machine for the license server.
  1. Patch the `/usr/local/maple/bin/maple.system.type` file with the following:
      
         ----- snip ------------------
    
*** maple.system.type.orig      Sun Jul  8 16:35:33 2001
      --- maple.system.type   Sun Jul  8 16:35:51 2001
    
***************
    
*** 72,77 ****
      --- 72,78 ----
                # the IBM RS/6000 AIX case
                MAPLE_BIN="bin.IBM_RISC_UNIX"
                ;;
      +     "DragonFly"|\
            "Linux")
                # the Linux/x86 case
              # We have two Linux implementations, one for Red Hat and
         ----- snip end of patch -----
  
  Please note that after the `"DragonFly"|\` no other whitespace should be present.
  This patch instructs  **Maple**  to recognize ***DragonFly*** as a type of Linux system. The `bin/maple` shell script calls the `bin/maple.system.type` shell script which in turn calls `uname -a` to find out the operating system name. Depending on the OS name it will find out which binaries to use.
  1. Start the license server.
  The following script, installed as `/usr/local/etc/rc.d/lmgrd.sh` is a convenient way to start up `lmgrd`:
      
         ----- snip ------------
      #! /bin/sh
      PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
      PATH=${PATH}:/usr/local/maple/bin:/usr/local/maple/FLEXlm/UNIX/LINUX
      export PATH
      LICENSE_FILE=/usr/local/maple/license/license.dat
      LOG=/var/log/lmgrd.log
      case "$1" in
      start)
      	lmgrd -c ${LICENSE_FILE} 2>> ${LOG} 1>&2
      	echo -n " lmgrd"
      	;;
      stop)
      	lmgrd -c ${LICENSE_FILE} -x lmdown 2>> ${LOG} 1>&2
      	;;
    
*)
      	echo "Usage: `basename $0` {start|stop}" 1>&2
      	exit 64
      	;;
      esac
      exit 0
         ----- snip ------------
  
  1. Test-start  **Maple** :
      
      % cd /usr/local/maple/bin
      % ./xmaple
  
  You should be up and running. Make sure to write Maplesoft to let them know you would like a native DragonFly version!

### 22.4.1 Common Pitfalls 


* The  **FLEXlm**  license manager can be a difficult tool to work with. Additional documentation on the subject can be found at http://www.globetrotter.com/.

* `lmgrd` is known to be very picky about the license file and to core dump if there are any problems. A correct license file should look like this:
      
      # ######################################################=
      # License File for UNIX Installations ("Pointer File")
      # ######################################################=
      SERVER chillig ANY
      #USE_SERVER
      VENDOR maplelmg
      FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \
               PLATFORMS#i86_r ISSUER"Waterloo Maple Inc." \
               ISSUED#11-may-2000 NOTICE" Technische Universitat Wien" \
               SN=XXXXXXXXX
  
   **Note:** Serial number and key 'X***ed out. `chillig` is a hostname.
  Editing the license file works as long as you do not touch the ***FEATURE*** line (which is protected by the license key).



CategoryHandbook
CategoryHandbook-linuxcompatibility