Core 6 to 9
||check: uname -a
||check: cc -v
||1.3.0 / 184.108.40.206
||check: Xorg -version
Fedora Core home page: http://fedora.redhat.com or
- 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
- 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 Fedora 7, 8 or
9 and glibc 2.6, 2.7 or 2.8: install the package "compat-libstcd++-33-3.*(i386)" either
Applications → Add/Remove
Software → Legacy Software
Development, or via su
-c 'yum groupinstall "Legacy Software Development"',
otherwise rpm installer of VFS would report "failed
- 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 Fedora
as Guast in VmWare5 or 6 is supported, but the GUI display
is slower than in native mode. Terminal i/o mode is also
ok, use "newfswin applic [-io=t]" from KDE or Gnome
console for VFS
of Visual FlagShip 6.1.*
the .rpm based package FlagShip-6.1.*_26.rpm, see INSTALL
file in the distribution ("less
INSTALL" ) for
- If the rpm installation
of FlagShip fails, i.e. when rpm reports "error: Failed
dependencies: libstdc++.so.5 is needed...", you need to
install the package "compat-libstdc++-33" either by yum,
or via rpm from the Fedora CD-ROM or DVD media, see above.
- The main FlagShip directory
- If you get get some warnings
at the end of FlagShip installation, or linker errors at static linking,
required package from Fedora CD-ROM or DVD distribution, or via yum.
- If in X/GUI environment
(KDE, Gnome etc): open console/terminal window.
- To test and run supplied
examples, invoke cd
/usr/local/FlagShip6/examples ; make
- If you get message "error
while loading shared libraries ... cannot
restore segment prot after reloc: Permission denied" at the time of
executing the application, you will need to set SELinux security
context for shared FlagShip library, see "Installation" paragraph
- Compile your
sources as described in fsman section FSC, e.g. "FlagShip
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
newfswin ./a.out #
for Textual i/o mode in X11 environment
- In some Fedora packages,
you may need to disable line 416 (#xrdb -merge ...) and enable
line 419 (source $FlagShipDir/bin/$xmapFile) in /usr/local/FlagShip6/bin/newfswin
to proper support Terminal i/o in X11 environment.
- The on-line manual is
available by entering "fsman &" in
for GUI mode, or "newfswin
fsman" for textual mode.
Manual in pdf format is available in /usr/local/FlagShip6/manual or
in Web. 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
- disable Unicode i.e.
set the environment variable "LANG=en_EN",
and start the application via newfswin.
See also and/or test with
- 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.
- If you have enabled new
kernel security extensions from the SELinux project
(default in Fedora 7, 8 or 9), and 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 will need to enable security context
for your shared FlagShip library by issuing : su
-c "chcon -t textrel_shlib_t /usr/local/FlagShip6/lib/libFlagShip6.so"
or disabling SELinux altogether in your /etc/sysconfig/selinux file by setting
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.
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).