Sponsored Content
Operating Systems Linux Red Hat Installing PHP tools using RPM in Redhat Linux Post 302872629 by Vicky81 on Saturday 9th of November 2013 12:05:15 AM
Old 11-09-2013
Installing PHP tools using RPM in Redhat Linux

Hi there,
I am trying to install few PHP tools in my Linux server by creating RPMs from source ( tar.gz) files. The issue here is that the tar.gz files does not have a configure file and so I am not able to do
./configure
make
install
opertations. I tried downloading src.rpms of these tools, but they have huge xml files that produce some syntax error and not able to proceed.

One example of the tool i tried to install is PHP-Code Sniffer.

Please help !!!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing RedHat Linux 7

Hey everybody. Its been awhile since I last posted but in short I am now in posession of RedHat Linux 7.0 which I got from a book called the RedHat 7 Bible. As this is not an official distribution I cannot get product support from RedHat so I decided to try here. I have three computers. I... (2 Replies)
Discussion started by: TheGoof
2 Replies

2. UNIX for Dummies Questions & Answers

Installing driver in linux redhat... what am I doing wrong?

I am trying to install this driver: http://www.asus.com/support/download/selectftp.aspx?l1_id=1&l2_id=15&l3_id=15&m_id=1&f_name=5702_558.zip~zaqwedc hoping it will correct my problem with my ethernet card. I am following the instructions in the text file that came with download... it says to... (7 Replies)
Discussion started by: Minnesota Red
7 Replies

3. UNIX for Dummies Questions & Answers

Installing php-4.3.3-2.i386.rpm

Ok when i try to run the install the is what i get How can i fix this can anyone help (8 Replies)
Discussion started by: Blackrose
8 Replies

4. Shell Programming and Scripting

Installing database through RPM

Hi everyone I have just joined a software developing team. I am new to unix. Basically we are developing a product, the problem is when the end user will install this package we would like to install the datbase associated with our product using RPM. Can it be done? how secure it is? and... (0 Replies)
Discussion started by: atul.saxena
0 Replies

5. UNIX for Dummies Questions & Answers

insturction for installing Apache and PHP on linux

Hello, Please give me stepwise instruction on installing Apache and PHP on linux. Thanks sheen (6 Replies)
Discussion started by: sheen
6 Replies

6. Red Hat

How to install expect after installing tcl on Redhat Linux

Hi, I have install tcl and then expect but I am getting below ouput while trying which expect which expect /usr/bin/which: no expect in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin) I have copied both in... (6 Replies)
Discussion started by: manish_1678
6 Replies

7. UNIX for Dummies Questions & Answers

Question on Redhat ver.6 RPM's

Hi, Using Redhat version 6.0, I need nmap so I have downloaded. But it requires many other dependencies, when I try to install it. See below err.msg. Is there any other way to get this installed, or I need to download each of the dependencies. rpm -Uhv nmap-5.51-2-mdv2011.0.x86_64.rpm... (3 Replies)
Discussion started by: samnyc
3 Replies

8. Red Hat

installing rpm from ISO

Hi, I would like to know is it possible to install rpm along its depedable rpm from mounted .iso image on Redhat Linux while installing rpm it is showing so many depandancy, so I would like to know with single command wheather it will take all depedable rpm from mounted iso image. (1 Reply)
Discussion started by: manoj.solaris
1 Replies

9. Red Hat

RedHat version in rpm spec files

Hi In opensuse we have this nice version control variable I use much when designing rpm spec files: rpm --showrc | grep suse_version %if 0%{?suse_version} > 0 && 0%{?suse_version} < 1700 -14: suse_version 1140But I do not find anything close to this in rhel/centos The only way... (0 Replies)
Discussion started by: mortenb
0 Replies

10. Red Hat

Issues installing inotify-tools on RedHat Linux

I wish to install inotify-tools-3.20.1-2.4.x86_64.rpm on Linux and fire inotifywait command. Initially i was looking for "inotify-tools-3.xx.tar.gz" as instructed here http://jensd.be/248/linux/use-inotify-tools-on-centos-7-or-rhel-7-to-watch-files-and-directories-for-events I have... (9 Replies)
Discussion started by: mohtashims
9 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)
All times are GMT -4. The time now is 06:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy