10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
I am getting the following error While installing Samba 3.4.1 on Solaris 10.
#./autogen.sh
./autogen.sh : autoheader : not found
./autogen.sh : test : argument expected
Please help me as I am in a critical state of the project.
Warm regards,
Sathya (10 Replies)
Discussion started by: sathya47
10 Replies
2. Programming
Hello. I'm using SunStudio 12 Update 1. When compiling for x86, everything works fine. When compiling for SPARC, I get the following errors. I linked libCstd.so.1 explicitly, but I get the same errors. Would anyone be kind enough to step me through resolving this? Thank you very much.
**... (2 Replies)
Discussion started by: acheong87
2 Replies
3. Infrastructure Monitoring
Hello all
Currently I am trying to install net-snmp-5.5 on a V480 Solaris 8 machine however things are hardly going smooth. I'm running configure will the following options.
./configure --prefix=/usr/local --with-mib-modules="smux ucd-snmp/diskio ucd-snmp/lmSensors host"... (2 Replies)
Discussion started by: krabu
2 Replies
4. UNIX for Dummies Questions & Answers
I am trying to learn how compile programs using this lesson.
UNIX Tutorial Seven
I am stuck at 7.4 Configuring and creating the Makefile. It stats that I need to configure the utility with my home directory. After doing the echo $HOME command I get /home/Bill_Gates. It then says to insert... (6 Replies)
Discussion started by: jae99
6 Replies
5. Solaris
How does one go aout compiling irssi locally on a fresh installation of Solaris 10,
Out put from ./configure m command
/download/1rss1-0.8.12
checking for a BSD-compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking for gawk... no
checking... (2 Replies)
Discussion started by: FloridaBSD
2 Replies
6. UNIX for Advanced & Expert Users
I'm trying to compile PHP5. I've installed mysql5 successfully and apache1.3 is working great, but I get the message
below when I compile PHP5. I double checked if I have libxml2 installed and I do. I installed libxml2 binary from
sunfreeware. Please see below for details:
./configure... (5 Replies)
Discussion started by: xnightcrawl
5 Replies
7. Programming
Hi,
I'm new to Unix. I'm trying to compile a shared library in Solaris running on x86. I get "void value not ignored as it ought to be" error when trying "make". But it compiles fine in Fedora. How can this happen? I think both are using the same type of compiler. What can I do to get around... (8 Replies)
Discussion started by: runnerb
8 Replies
8. Solaris
Hi everyone,
I have SUn E250 server running solaris 10. I have installed apache 2 + MySQL + PHP-5.1.4 following the guidelines on this website
http://meljr.com/~meljr/AMPSolaris10.html
Excellent document for first time installation. Now, because I wanted to use Coppermine Photo Gallery, I... (9 Replies)
Discussion started by: callingrohit
9 Replies
9. UNIX for Advanced & Expert Users
I have a problem, my mate built me a little home server using Unix and after he set everything up he deleted the main compiler so i wouldnt be able to Install/Compile any software...
And now i wanted to Install a compiler and i have to compile it...
thats like installing winzip from a zip... (3 Replies)
Discussion started by: l22
3 Replies
10. UNIX for Dummies Questions & Answers
I am new to unix so please forgive ignorance. I am running openbsd-2.9 and need some help. All the software I run was added via the package system openbsd has. There have been times when I need an app. But it was not in the openbsd ports and or packages system. I usually just wait for it to show up... (3 Replies)
Discussion started by: Blunt_Killer
3 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)