FlagShip
Tech Info
|  |
RedHat
9.x and Enterprise 3, 4, 5 ES
| tested with |
version : |
9 |
|
check: CD or DVD label |
| |
kernel : |
2.4, 2.6 |
|
check: uname -a |
| |
gcc : |
3.2.2, 4,x |
|
check: cc -v |
| |
glibc : |
2.3.2 |
|
check: /lib/libc.so.6 |
| |
X11 : |
XFree86 4.3.0 |
|
check: XFree86 -version |
RedHat home page: http://www.redhat.com
Linux Installation
Hints:
- Packages: in
addition to default suggestions and your choices,
- choose "Workstation " or "Server" for
the installation type
- select "Customize Software Selection", enable "Development" and
"X Software Development"
- check in "Select
individual packages" for enabled Development/Languages:
gcc, gcc-c++, compat-gcc*, and Development/Libraries:
XFree86-devel, glibc-devel, libjpeg-devel, libstdc++-devel,
ncurses-devel (required for static linking)
- with RH ES 4 or 5 and
glibc 2.6 or 2.7: check/install "Legacy
Software Development" package from your
Linux distribution, or via su
-c 'yum groupinstall "Legacy
Software Development"' otherwise
rpm installer would report "failed
dependencies libstdc++.so.5"
- for running executables
in Terminal i/o mode using "newfswin" script, you will need installed
csh/tcsh, either from the Linux media, or from http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/csh
- Running RedHat
as Guast in VmWare5 & 6 is supported, but
the GUI display may be slower than
in native mode. Terminal i/o mode is also
ok, use "newfswin applic [-io=t]" from
KDE (or Gnome) console for VFS
applications.
Installation
of Visual FlagShip 6.1.x:
- Install
the .rpm based package FlagShip-6.1*_26.i386.rpm, see INSTALL file
in the distribution ("less
INSTALL") for
details
- The main FlagShip directory
is /usr/local/FlagShip6
- RedHat supply all required
static libraries in packages suggested above,
so you may compile both dynamically (default) and statically (using
the
-stat compiler switch). If you get get some warnings at the end of
FlagShip installation, or linker errors at static linking, post-install
the
required packages noted above from the RH CD-ROM or DVD distribution
via redhat-config-packages or Main Menu → System settings → Add/remove
applications.
Using FlagShip:
- If in X/GUI environment
(KDE, Gnome etc): open console/terminal window.
- Compile your
sources as described in fsman section FSC, e.g. "FlagShip
myapp*.prg",
a short help is available via "FlagShip
-h". Note the case sensitive names in Unix/Linux.
- Watch for displayed compiler
and linker errors, and fix if any.
- If everything is ok,
execute (see fsman section FSC):
./a.out # in
GUI mode
newfswin ./a.out #
for Textual i/o mode in X11 environment
- The on-line manual is
available by entering "fsman &" in
KDE/Gnome console
for GUI mode, or "newfswin
fsman -io=t" for textual mode.
Printed
manual is available upon request.
- Step-by-step instruction
for converting available applications to GUI is given in
fsman section LNG.9.6
- Examples are
available in /usr/local/FlagShip6/examples and .../tools
directory. Best to copy them to your working directory.
- On problems or questions,
please check the on-line manual and FAQ first. If
your problem persist, contact FlagShip support -
we grant free tech support not only for the licensed,
but also for the Test/Eval version.
Known Issues :
- If the PC-8 semi-graphic
characters are displayed in textual mode as Ä's
(A-umlaut) etc, you eiter may either
- start the application via newfswin, newfscons or newfsterm (see
above and Release Notes in fsman) which automatically sets the proper
environment, or
- disable Unicode i.e.
set the environment variable "LANG=en_EN",
and start the application via newfswin.
See also and/or test with
/usr/local/FlagShip6/examples/boxcommand.prg
- If the last character in
the manual pages seems to be missing in GUI mode, select Courier[adobe]
via Menu→Options→Font→Input/Output or assign other
font via command-line parameter, see fsman -h for furtehr
details.
Notes for Linux Enterprise 4 ES with
gcc 3.4 (kernel 2.6.9)
- The displayed gcc 3.4 warning "cc1:
note: -fwritable-strings is deprecated; see documentation for details" is
harmless and can be ignored.
- When the linker reports "/usr/bin/ld:
warning: libstdc++.so.5, needed by
/usr/local/FlagShip6/lib/libFlagShip6.so not found", you will
need to install compat-libstdc++-33-3.2.3-47.3.i386.rpm package from RedHat
CD#2
Notes for Linux Enterprise
4 and 5 ES with enabled SELinux
- if
you get "error
while loading shared libraries: /usr/lib/libFlagShip6.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 RedHat & Fedora feature.
Go into System -> Administration -> Security
level, select the SELinux tab, expand the Compatibility category, and tick
the box next to Allow the use of shared libraries with text relocation.
Alternatively, invoke in
terminal: su -c "chcon
-t textrel_shlib_t /usr/local/FlagShip6/lib/libFlagShip6.so"
Additional Info:
Since FlagShip translates the Xbase code to C code as an intermediate step and requires object compatible libs during the linking stage, C compilers, utilities and libraries must be chosen with great care, otherwise upredictable errors may occur.
The
C compiler (and the optional static libs) is required only in the
developing phase, it is not required
for the user of your application, which only needs the by FlagShip
produced executable (i.e. your own application
executables, see also fsman section SYS.1.2 for distribution hints).
|