Installation of FlagShip 7 (Visual FlagShip) for Linux ------------------------------------------------------ This FS7 (VFS) will be installed in the /usr/local/FlagShip7 directory. Note: For special cases, e.g. to enable maintaining of older applications created by FS 4.4*, FlagShip 7 may co-exist with FlagShip 4.48 and/or FlagShip 5 or 6 installed on the same system. Please refer to the README for handling of multiple FlagShip's installations on the same system. There are three Visual FlagShip ports available a) release 7.* for kernel 2.6 (prefered for current Linux distributions) files: FlagShip-7*_linux26.tgz = non-rpm installation FlagShip-7.*-26.i386.rpm = rpm installation Applicable for Linux with kernel 2.6, gcc 4.x, glibc 2.8 and newer e.g. for: RedHat 9-10, RH Enterprise 4-5, Fedora 6-11, Conectiva 9-10, SuSE 10-11, SuSE SLES 10, Mandrake 10, Slackware 9-10 etc. b) release 7.* for kernel 2.4 and 2.6 (compatible to older Linux) requires "compat-libstdc++" or "libstdc++33" for some kernels 2.6 files: FlagShip-7*_linux2426.tgz = non-rpm installation FlagShip-7*-2426.i386.rpm = rpm installation Applicable for Linux with kernel 2.4-2.6, gcc 3.2-4.x, glibc 2.3 to 2.8 e.g. for: RedHat 9, RH Enterprise 3-5, Fedora Core, Conectiva 9-10, SuSE 8.2-11.x, SuSE SLES 9-10, Mandrake 10, Slackware 9-10 etc. c) release 7.* for kernel 2.4 and 2.2 (old Linuces) files: FlagShip-7*_linux24.tgz = non-rpm installation FlagShip-7*-24.i386.rpm = rpm installation Applicable for Linux with kernel 2.2-2.4, gcc 2.95-3.1, glibc 2.2-2.3 e.g. for: RedHat 7 and 8, SuSE 7 and 8, Conectiva 8 etc. All releases are equivalent but are different ports (target systems) Please check frequently http://www.fship.com/whatsnew.html for updates, new releases and additional info. 1) FS7 Requirements: ------------------- - Linux kernel 2.2 to 2.6 based (check: uname -a), - corresponding gcc (check: /lib/libc.so.6) and gcc (check: cc -v) - XFree86 Version 4.1.x or 4.2.x (check: XFree86 -version), or X.Org 1.4.x (check: Xorg -version) - libc.a and libstdc++*.a libraries (for statically linked applic) - Activation key (Eval, Personal or Pro version) for Linux based FlagShip-7/VFS port, available from - 60 MB free disk space - 256 MB RAM (more is better) 2) Required Linux packages -------------------------- Before installing FlagShip, you sould install following packages from your Linux distribution: - gcc - gcc-c++ and for the 2.4+2.6 compatibility port *2426* (see (b) above) - compat-gcc (also named "compat-gcc-34" or "compat-glibc" or "Legacy Software Development") and "compat-libstdc++" (if extra) packages from your Linux distribution, otherwise rpm installer may report "failed dependencies: libstdc++.so.5" and for static linking (if such is required) - XFree86-devel, glibc-devel, libjpeg-devel, libstdc++-devel, ncurses-devel For executables running in GUI mode, X11 needs to be installed and active. To run executables in Terminal i/o mode using "newfswin" script, you will need installed tcsh or csh, either from the Linux media, or from http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/csh FlagShip installer checks for them and will prompt you when anything is missing. 3) Installation --------------- Syntax used here: [%] is a mark for user promt, [#] is a mark for root/su prompt. Don't type these marks, but enter the commands behind. ## is a comment mark, don't type it nor the rest of the line Note for (d..f): root or su mode is required to create links to /usr/bin and /usr/lib. If you cannot get su user, you at least must have rwx access rights to /usr/local/FlagShip7/bin and ./lib directories and rw access rights to files there and also will need to add PATH=/usr/local/FlagShip7/bin:$PATH in your start-up/login script (usually ~/.bashrc). a) If you are updating, i.e. have previously installed older FS4, VFS5, VFS6 or VFS7 release, uninstall the "old" release first: [%] su [#] FS7uninstall ## when VFS7 is already installed [#] FS6uninstall ## optionally, to uninstall VFS6 [#] FS5uninstall ## optionally, to uninstall VFS5 [#] FSuninstall ## optionally, to uninstall FS4 b) If you are using media downloaded via Internet (either rpm or non-rpm based): [%] su [#] mkdir /tmp/fs7_inst ## or any directory of your choice [#] cd /tmp/fs7_inst [#] tar xvzf /my/download/dir/fs7linux*.tgz ... you will get this INSTALL and a README file and FlagShip-7.1-04*.rpm or FlagShip-7104*.tgz file continue with step (d) or (e) c) If using FlagShip 7 CD-ROM: ... insert the CD-ROM in drive [%] su ... mount the CD-ROM, e.g. "mount /cdrom" or "mount -r -t iso9660 /dev/hdc /cdrom", best to check /etc/fstab when the CD-ROM is already configured ... invoke the installation script which guides you thru the installation [#] cd /cdrom [#] sh ./setup.sh ... or for manuall installation, continue with step (d) or (e) d) To install the rpm based distribution of VFS7: [%] su - for release 7.1.04_26 (see above) from downloaded media: [#] cd tmp/fs7_inst [#] rpm -ih FlagShip-7.1-04_26.i386.rpm - for release 7.1.04_26 (see above) from CD-ROM: [#] cd /cdrom/Linux/FlagShip7/kernel_2.6 [#] rpm -ih FlagShip-7.1-04_26.i386.rpm - for release 7.1.04_24 (see above) from downloaded media: [#] cd tmp/fs7_inst [#] rpm -ih FlagShip-7.1-04_24.i386.rpm - for release 7.1.04_24 (see above) from CD-ROM: [#] cd /cdrom/Linux/FlagShip7/kernel_2.4 [#] rpm -ih FlagShip-7.1-04_24.i386.rpm (Note: When using the command "rpm -Uh FlagShip*.rpm" the previous FlagShip versions will be overwritten, incl. FS4.48) [#] cd /usr/local/FlagShip7 [#] make ## or: [#] ./FS7install ... enter the serial number and activation key for VFS7 (Note: you cannot use the Activation data of FS4.48 nor of FS5 or FS6. If you have not the Activation key yet, go to http://www.fship.com/eval.html for a free Test/Eval version) [#] exit ## the su mode f) To install non-rpm based distribution (e.g. on Slackware or Debian), a simple un-tar is used: [%] su [#] cd /usr/local ## recommended, will install in /usr/local/FlagShip7 - for release 7.1.04_26 (see above) from downloaded media: [#] tar xvzf /tmp/fs7_inst/FlagShip-7104_linux26.tgz - for release 7.1.04_26 from CD-ROM: [#] tar xvzf /cdrom/Linux/FlagShip7/kernel_2.6/FlagShip-7104_linux26.tgz - for release 7.1.04_24 (see above) from downloaded media: [#] tar xvzf /tmp/fs7_inst/FlagShip-7104_linux24.tgz - for release 7.1.04_24 from CD-ROM: [#] tar xvzf /cdrom/Linux/FlagShip7/kernel_2.4/FlagShip-7104_linux24.tgz [#] cd /usr/local/FlagShip7 [#] make ## or: [#] ./FS7install ... enter the serial number and activation key for VFS7 (Note: you cannot use the Activation data of FS4.48 nor of FS5 or FS6. If you have not the Activation key yet, go to http://www.fship.com/eval.html for a free Test/Eval version) [#] exit ## the su mode 4) Deinstallation: ----------------- The whole FlagShip 7 (VFS) package is unistalled by: [%] su [#] FS7uninstall ## (includes also rpm deinstallation) or: [#] rpm -e FlagShip-7 ## (partial, does not remove links !) or: [#] cd /usr/local/FlagShip7 ; make clean [#] exit ## the su mode 5) Installation details: ----------------------- As opposite to FlagShip-4.48, which install files in /usr/bin, /etc, /usr/lib and /usr/FSsrc directories, VFS5, VFS6 and VFS7 is installed mainly in the /usr/local/FlagShip* directory and in subdirectories below, here /usr/local/FlagShip7/* Instead of copying files, the installation script FS7install creates following symbolic links from the /usr/local/FlagShip7/* directory: ./bin/FS7uninstall -> /usr/bin/FS7uninstall (if possible) -> /usr/local/bin/FS7uninstall (alternative) ./bin/FlagShip -> /usr/bin/FlagShip (if possible) -> /usr/bin/FlagShip7 (if possible) -> /usr/local/bin/FlagShip (alternative) -> /usr/local/bin/FlagShip7 (alternative) -> /usr/bin/FS7 ./bin/fsman -> /usr/bin/fsman (old fsman renamed to fsman4) -> /usr/bin/fsman7 ./lib/libFlagShip7104_26.a -> /usr/lib/libFlagShip7104_26.a ./lib/dynFlagShip7104_26.o -> /usr/lib/dynFlagShip7104_26.o ./lib/libFlagShip7104_26.so -> /usr/lib/libFlagShip7104_26.so ./terminfo/f/* -> /usr/share/terminfo/f These links will be removed automatically by "FS7uninstall" script, see (3) above. 6) Backward compatibility: ------------------------- When you already have FS4 or VFS5, VFS6 Makefile's or compilation scripts, you may continue to use them "as is" when you invoke the compiler by "FlagShip" and have deinstalled previous releases. On multiple FS installation, change the compiler to "fs7", see details in README file. Note that you will need to recompile all the .prg files by VFS7 and rebuild the indices created by FS4 or Clipper. Indices created by previou VFS5 or VFS6 release are fully backward compatible. See further details in the README file. 7) Additonal notes for SELinux ------------------------------ If you have enabled SELinux, and get "error while loading shared libraries: /usr/lib/libFlagShip7*.so: cannot restore segment prot after reloc: Permission denied" at the time of invoking dynamically linked executable, you need to modify the SELinux policy to permit loading of shared libraries. This is a SELinux feature. Invoke in terminal su -c "chcon -t textrel_shlib_t /usr/local/FlagShip7/lib/libFlagShip7*.so" Read next: the README file and /usr/local/FlagShip7/docu/how-to* files.