RUNAPP(1) Listaller Project RUNAPP(1)NAME
runapp - Run an application
SYNOPSIS
runapp {APPNAME}
DESCRIPTION
This manual page documents briefly the runapp command.
runapp runs applications installed using Listaller. It will set the application environment, initiate a sanbox and do everything else
needed to run the application. runapp can also execute every other application found on the system, even those which were not installed
using Listaller.
OPTIONS --version
Display version number of runapp
--verbose
Turn on verbose mode (this can be used for debugging).
SEE ALSO
lipa (1).
Additional documentation can be found on http://listaller.tenstral.net.
AUTHOR
This manual page was written by Matthias Klumpp matthias@tenstral.net.
COPYRIGHT
Copyright (C) 2009-2012 Matthias Klumpp
Listaller Project 18 April,2012 RUNAPP(1)
Check Out this Related Man Page
LIGCC(1) Listaller Project LIGCC(1)NAME
ligcc - Wrapper around gcc to create more portable apps
SYNOPSIS
ligcc [OPTION ...]
DESCRIPTION
This manual page documents briefly the ligcc command.
ligcc is a wrapper around gcc. It allows you to create more portable executables by doing three things:
o Forces the linker to link against older glibc symbols. Users who are using an older version of glibc will no longer get "undefined
symbol GLIBC_2.4 in /lib/libc.so"-style error messages.
o Allows you to easily statically link to any other library.
o Automatically removes bogus dependancies. For example, your program uses libfoo. libfoo uses libpng internally, but your app does not.
Yet the pkg-config file for libfoo specifies "-lfoo -lpng" is linker parameters. And tadaa - you now have a bogus dependancy on libpng!
LiGCC automatically removes the -lpng for you if your app doesn't use libpng directly.
o Add $ORIGIN/../lib to the binary's library search path. $ORIGIN is the directory in which the binary exists. This ensures that your
binary can find library dependencies which are placed in the 'lib' folder under the same prefix. You might want to install custom
libraries into /lib. If you set $APBUILD_PROJECTNAME, ligcc will also add $ORIGIN/../lib/$APBUILD_PROJECTNAME to the library search
path.
OPTIONS
See the manpage of gcc(1) for more information about possible options.
There are also several environment variables available to modify ligcc's behavior check the documentation for more information.
SEE ALSO
lig++ (1), gcc(1).
Additional documentation can be found on http://listaller.tenstral.net.
AUTHOR
This manual page was written by Matthias Klumpp matthias@tenstral.net.
COPYRIGHT
Copyright (C) 2009-2012 Matthias Klumpp
Listaller Project 20 April,2012 LIGCC(1)
Hi all,
I have an input file like
trk 1 soft
trk 1 get
trk 1 get
trk 1 soft
Want to have output file contains line number of lines which have "soft" string from input like
1
4
Then, create new file from output to
ui 1 stop
ui 4 stop
Tried using with awk, still not got result.
... (13 Replies)
Hello Everyone,
I am logged in as me. I created a script in the directory "/install/new" called "script1.sh" which basically runs another script "runapp.sh" . The "runapp.sh" is a vendor provided application strart up script that came with the installation. This is also in the same directory as... (10 Replies)
Hello,
AIX v6.1 TL6
I need to install websm and have problems configuring AIX embedded Web server.
In order to install windows client I must download it from AIX server using HTTP.
This is from official IBM doc:
I am able to launch configassist successfully but there is no word about websm... (0 Replies)
Hi Guys, I want to create a shell script to run multiple jobs in sequence.
Explaination -
If I were to run each jobs individually I would have gone to folder - "abin"(where my shellscript is place) as follows
cd abin
abin > runappeng.sh abc001
Now, I have list of programs which are like... (8 Replies)