9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am not a newbie to Linux, i have been using Linux as my desktop for 4 years, but i am just an end user to Linux, no advanced knowledge to it.
I knew that, i can download generic linux kernel and compile it by myself, but how about Unix? how can i get an Unix kernel and compile it ? or no this... (5 Replies)
Discussion started by: wong.sie.ung
5 Replies
2. Programming
I am trying to compile a proc++ program on linux using an 11.2 client
and pointing to a 10.2 database running on Solaris. The compiler is able
to connect to the database but the semantic checks fail as if it cannot see
any objects in the database. I tried a test, only selecting 'X' into a... (0 Replies)
Discussion started by: rdudash
0 Replies
3. Linux
Hi ,
I am exploring the nmap utility for Linux.
I know that, nmap binaries are specific to the platforms e.g. nmap binaries will be diferent for Windows , AIX , Solaris and Linux platforms.
Can anyone tell me , will the nmap binaries be different for different flavours of Linux such as... (1 Reply)
Discussion started by: jatin56
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
as my thread has been moved to Debian.
I don't run Debian machine.
My machine is Linux embedded router - mipsel.
Sources come from Debian, but Dialog sources are GNU,
so no Debian specific.
Native compilation vs. crosscompilation,
exactly to let you know, that I don't run Debian... (2 Replies)
Discussion started by: jack2
2 Replies
5. UNIX for Dummies Questions & Answers
I am a Linux noob, and have been trying to compile some source in Linux and I am lost. I am a game modder and I have some open source code which I have compiled in windows a million times but now I need to compile in Linux.
If this thread fails to help me, I will credit anyone who can... (4 Replies)
Discussion started by: fire_noob
4 Replies
6. BSD
Hi ,
I have freeBSD installed. I need to compile a c program which has embedded informix sql statement in it.
Can you please help me to to do the same. I need to know what I should I do to make BSD compatable to compile the c program ?
Thanks in advance
Jisha (3 Replies)
Discussion started by: jisha
3 Replies
7. Programming
Just that the Subject says.
I am looking for a C compiler for Linux x86 that will allow me to compile a C source code file and the resulting binary will be able to run on a Sparc running Solaris.
Thanks. (2 Replies)
Discussion started by: lyonsd
2 Replies
8. Programming
I have a trouble: i cannot install and use freeBSD for some reasons(have no computer now, and comps on my work are Windowsed), but I need to compile some UNIX sources for freeBSD(this one: http://ppcpp.sf.net/). What can I do? Are there a compilers, that can run in Windows, but can compile binaries... (3 Replies)
Discussion started by: szzz
3 Replies
9. Programming
hi everyone,
i am a beginner of C and doing a subject which involved c programming under unix.
i tried compile the c program under linux. but i can only get the a.out file in /usr/bin, not in the current dir. can anyone know how to change the sys. configration. Please help. thanks (2 Replies)
Discussion started by: ctchung
2 Replies
ATTILA(1) Alliance - attila User's Manual ATTILA(1)
NAME
attila - A Tool Installer
SYNOPSIS
attila [ -h ] [ -S ] [ -U ] [ -F ] [ -A ]
[ --help ] [ --ssh ] [ --user ] [ --asim ]
[ --prefix=INSTALL_DIR ] [ --builddir=BUILD_DIR ]
--tool=name1 [ --tool=name2... ]
[ -c- configure_arg1 [ configure_arg2 ... ] ]
[ -m- make_arg1 [ make_arg2... ] ]
DESCRIPTION
attila automates the process of compiling and installing one or more Alliance tools. The tool can be installed either in the user's account
(during the devellopment stage) or in the Alliance system wide tree (for instance /asim/alliance) when a new version is made avalaible to
all.
attila proceed with the following steps :
1. Checks if the sources of tools are present in the user's account. If not, check them out from the Alliance CVS tree. Note that you
must have access to it.
2. In case of --asim or --full installations, attila will fork itself on one Linux computer (currently bip) and on one Solaris computer
(beny). As to connect on thoses computer it will uses rsh so you must setup your ~/.rhosts to access them whithout passwords. You
also can uses ssh (but the procedure to allow automatic login is more complicated).
3. Run autostuff for the tool in the ~/alliance/src directory.
4. Run configure in the build directory (see below).
5. Install the tool in the local install directory (see below) or in the system-wide Alliance directory rooted under /asim/alliance.
After an --asim install: the build directory tree of the tool will be removed to avoid messing with further local installations.
DIRECTORY STRUCTURE
attila relies on the following tree structure : (all paths below are given relative to the user's home directory)
o ~/alliance/src where the tools sources are to be found.
o ~/alliance/Linux/build/$TOOL : the top directory under which the tool will be compiled for Linux. This is where the configure script
will be run.
o ~/alliance/Linux/install : the top of the install tree when the tool is compiled locally for Linux. Under this directory you will found
(at least) : ./bin, ./lib and ./include.
o ~/alliance/Solaris/build/$TOOL : the tool's build directory for Solaris.
o ~/alliance/Solaris/install : top of the local install tree for Solaris.
CVS CHECKOUT
If the sources of the requested tool(s) are not found under ~/alliance/src/ attila will try to check them out. So, as says above, you must
have access rights to the Alliance CVS tree.
In addition to the tool(s) sources, it will also checks for the minimal set of files needed for configure to run. As for now :
o autostuff
o alliance.m4
o motif.m4
o Makefile.am
GUESSING CVSROOT
The root of the CVS tree will be set according to the following rules :
1. Uses the user's environment variable CVSROOT if sets.
2. Uses the attila default value sets in attila.conf (variable ATTILA_CVSROOT).
GUESSING ALLIANCE_TOP
The root of the Alliance installed distribution tree will be set according to the following rules :
1. Uses the user's environment variable ALLIANCE_TOP if sets.
2. Uses the attila default value sets in attila itself (variable ATTILA_ALLIANCE_TOP).
ALLIANCE_TOP: is set in attila itself because its value is a prerequisite to load the configuration file attila.conf which is in the
directory $ALLIANCE_TOP/etc/.
ARGUMENTS
attila accepts the followings arguments :
o -h, --help : print help.
o -S, --ssh : uses ssh instead of rsh to connect to the remote computers (in case of --asim or --full).
o -U, --user : perform a local installation.
o -F, --full : install for all avalaibles architectures (currently Linux and Solaris).
o -A, --asim : install in the system-wide directory (/asim/alliance).
o --prefix=INSTALL_DIR : override the default installation directory.
o --builddir=BUILD_DIR : override the default building directory.
o --tool=name1 : name of the tool to be installed.
o -c- configure_arg1 : all arguments following -c- (until a -m- is encountered) are passed as is to the subsequent call to configure. For
example, if you want to first use your local libraries, give --enable-devel. If you want to link or install dynamic libraries, give
--enable-alc-shared for alliance libraries and give --enable-shared for other libraries.
o -m- make_arg1 : all arguments following -m- are passed as is to the subsequent call to make. If no -m- argument is given, then install is
assumed. If you want to completly uninstall a tool and clean it's build directory you can pass uninstall clean
CONFIGURATION FILE ATTILA.CONF
The configuration file is located in $ALLIANCE_TOP/etc. This file is to be read by the sh shell. It sets up the following variables :
o LINUX_TARGET : the computer where to compile for the Linux architecture (default bip).
o LINUX_CC : the name or full path to to the C compiler for Linux system (default gcc3).
o LINUX_CXX : the name or full path to to the C++ compiler for Linux system (default g++3).
o SOLARIS_TARGET : the computer where to compile for the Solaris architecture (default beny).
o SOLARIS_CC : the name or full path to to the C compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3).
o SOLARIS_CXX : the name or full path to to the C++ compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3).
o ATTILA_CVSROOT : the root of the Alliance CVS tree (default /users/outil/alliance/cvsroot).
o CVS_STARTUP_FILES : the minimal set of files needed to run configure.
EXAMPLES
Compile & install nero tool on the local computer (must be either a Linux or a Solaris one) :
$ attila --tool=nero
Compile & install nero tool for all architectures (currently only Linux and Solaris are supported) :
$ attila --full --tool=nero
Compile & install nero tool in the system-wide directory (a new version for everyone to use) :
$ attila --asim --tool=nero
Compile & install mbk then genlib (the order is significant) in a row for a local install on the current computer :
$ attila --tool=mbk --tool=genlib
Compile nero tool and link it against the locally installed libraries (if any).
$ attila --tool=nero -c- --enable-devel
Remove poire tool from the system-wide tree. (poire is the old name of nero).
$ attila --asim --tool=poire -m- uninstall
ASIM
/LIP6 13 October 2002 ATTILA(1)