Tech Info
Linux compatibility and available ports, Download Links
Linux systems have been developing rapidly over the past few years . Due to this, the compatibility of the basic system (kernel) and dependent tools (compiler, utilities, libraries) is not fully continuous but was done in more or less incompatible steps. More...Since FlagShip translates the Xbase code to C code as an intermediate step and requires object compatible libs during the linking stage, matching kernels, C compilers, utilities and libraries must be chosen with great care. To ensure full Linux compatibility, there are different FlagShip ports available for x86 Intel/AMD based Linux (here listed from newest to oldest):
| Linux Distribution e.g. | Kernel | Glibc | Gcc | Visual FlagShip 6.1.19 | FlagShip 4.48 | ||||||||||||
|
(2.4
to ) 2.6 |
2.3.2 |
3.1 |
|
sorry, 4.48 is not supported for kernel 2.6 and gcc 4 anymore, see below for older versions or update to VFS 6 | ||||||||||||
|
RedHat 9.0, RH Enterprise 3 Fedora Core 2 & 3 SuSE 8.1 to 9.3, SLES9 Conectiva 8.x, 9.0, 10 Mandriva/Mandrake 9, 10.0, 10.1 Debian 3.0, 3.1 Slackware Stable 9.x, 10.1, 10.2 |
2.4.x |
2.3.x |
3.1 |
same as above
|
available
on CD-ROM, see compatibility note below |
||||||||||||
RedHat 7
and 8 |
(2.2.x to ) 2.4.x |
2.1.x to 2.2.x |
2.95
to 2.96 |
|
|
||||||||||||
| RedHat 7.x, Conectiva 7 | 2.2.x |
2.2.x |
2.97 |
see above |
available on CD-ROM | ||||||||||||
| SuSE 5.x-6.x, RedHat 5.x-6.x | 2.0
- 2.1 |
1.x - 2.0 | 2.x | n/a | available on CD-ROM | ||||||||||||
Additional porting details (*)... If you wish to use or test FlagShip for other operating systems, see the Windows or Unix ports.
Please choose the FlagShip port carefully according to your used Linux system. In doubt, check the availability and links of /lib/libc.so.6 as described above and the used cc/gcc version first, then order or download the corresponding FlagShip port.
Compatibility note: the kernel release is not fully relevant for the Linux base, since you may re-compile nearly any kernel on nearly any Linux base. The only reliable criterion is the Linux libc.so library and the accompanying gcc release. These may differ significantly and are unfortunately often incompatible to each other, refer to gcc Release notes. Therefore:
Warning: using a FlagShip port incompatible to your Linux system or with different cc/gcc may cause unpredictable behavior, unresolved externals or even core dump or segmentation or a suspicious message like "Serial number corrupted" and so on, since these Linux versions, compilers and libs are often incompatible to each other. Also the linker message undefined reference to `__ctype_b' signals an incorrect (incompatible) FlagShip port to your Linux. However the by FlagShip produced executables will most probably run well without problems also on other Linux sub-releases, especially if linked statically. See further details in the FAQs.
Requirements:
Depending on the used Linux system and
FlagShip port, you will need to have installed GNU C (gcc) compiler
(and the accompanying libs and include's) to be able to develop with
FlagShip. Check with "cc -v".
* For backward compatibility
of libstdc++.so.6 (used with glibc 2.6 or gcc 4.x and later) to
libstdc++.so.5, you will need to install the package named "compat-libstdc++" or
"compat-libstdc++-33*" or similarly (see the Note: the C compiler is not required
for the user of your application, which only needs the by FlagShip
produced executable. See also section SYS.1.2 of the FlagShip manual
for further details how to customize your application. More...
button
above), otherwise FlagShip rpm installer may report "failed
dependencies libstdc++.so.5" and/or the linker will report "warning:
libstdc++.so.5 not found"
When using 64bit kernel version (Linux
x86_64), read this information.
The required disk space on the /usr file system is approx. 25 MBytes for the FlagShip 4.x and 50 Mbytes for the Visual FlagShip 6.x installation. Check the available space with "df /usr".
FlagShip can either be installed
- via "rpm" (Linux packager, suggested e.g. for RedHat, FedoraCore, SuSE, Conectiva, Mandrake/Mandrovia and similar distributions) by using the rpm-based FlagShip package,
- or via install script and tar archive (e.g. for Slackware, Debian etc.) by using the non-rpm-based (i.e. tar-based) FlagShip package.
For both packages:
- un-tar the downloaded file (e.g. "tar xvzf /my_download_path/fs6*.tgz") into an empty directory,
- and read the installing instruction ("less INSTALL") for detailed step-by-step description.
Alternatively, CD-ROM distribution is available at moderate s&h cost (contact your dealer, distributor or multisoft).
With a slow Internet access, you may download the package without PDF manual (approx. 2500 pages) and access or download it later using the manual link on the FlagShip home page. You also may order printed version of the manual. An on-line manual named "fsman" is available in any distribution.
You may confirm the integrity of files you download by the MD5 utility by using MD5sum message digests. If you wish to test or use FlagShip for other operating systems, see the MS-Windows or Unix ports.
Licenses:
There are free licenses for test/evaluation purposes or personal non-commercial use, as well as commercial licenses available. See the price list and license terms for additional details. You may test FlagShip for free, simply fill-in this form and submit. When you already own FlagShip license and want to upgrade to another Linux system, contact your dealer or multisoft.