Sponsored Content
Full Discussion: Setting path for GCC?
Top Forums UNIX for Dummies Questions & Answers Setting path for GCC? Post 40461 by cbkihong on Tuesday 16th of September 2003 02:09:09 AM
Old 09-16-2003
Just from your log it seems 3.3.1 is used, because gcc -v gives 3.3.1. On many systems, /usr/local comes before /usr in PATH. So if you have a version in /usr/local, it is usually the one that is loaded if you don't qualify with the absolute path.

You shouldn't delete 3.2, and in fact you should generally not remove the system-shipped gcc from your system.

If I don't interpret wrongly, because all of your libraries shipped in your RPMs were compiled using gcc 3.2, if you later on want to compile packages using these libraries, your gcc3.3 will not link those libraries unless they are recompiled using the new compiler. If you force remove gcc3.2 I guess you will break a lot of things. That's what I was told, and I need clarification on this too. gcc is not just another software package. It is the central component of any Linux and BSD systems that affects many parts of the system, and if that is not done carefully, you will likely wreck your system.

If you really have to stay with the latest compiler, use Debian unstable, because packages of the libraries compiled with that compiler will also be available with each compiler release. For example, the gcc version I have here is 3.3.2 with all necessary patches. That is by far the safest way to go.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help on setting path variable

Hi there, I need help on setting the path variable. How can I set the path variable with Bourne Shell. My scripts goes like this, but did not work. #!/bin/sh PATH=/usr/bin:/usr/ucb:/etc:/export/home/zchen/home export PATH Thanks, Z (4 Replies)
Discussion started by: randomcz
4 Replies

2. Shell Programming and Scripting

Setting path

Hi all, I have a java command in a shell script. When i m executing the command from the prompt its working fine. But when i paste the same command in a shell script and execute the shell script it says path not found. Please help. (5 Replies)
Discussion started by: radhika03
5 Replies

3. Solaris

Problem Setting $PATH

I am trying to install the pkg-get package to a fresh install of Solaris 10. I am able to download and install correctly using the default directory for both pkg-get and wget as found on blastwave.org. When I issue the command "which wget and which pkg-get" it returns no wget or pkg-get found in... (1 Reply)
Discussion started by: greengrass
1 Replies

4. Shell Programming and Scripting

Setting up a path in UNIX

I have the following script "test". When i tried to execute it, I am not able to run it. I dunno why ? Then i tried getting the first few lines of the script which is displayed below: $head -10 test #!/bin/ksh PROG=$0;export PROG ORAUSER=`get_inf_env INFORM_DB_ACCOUNT`;export ORAUSER... (13 Replies)
Discussion started by: bobby1015
13 Replies

5. Shell Programming and Scripting

Setting path names

I am in a directory called /abstracts Doing tree -d gives . ├── geo1936 │ ├── geo01n01 │ ├── geo01n02 │ └── geo01n03 ├── geo1937 │ ├── geo02n01 │ ├── geo02n02 │ ├── geo02n03 │ └── geo02n04 (4 Replies)
Discussion started by: kristinu
4 Replies

6. UNIX for Dummies Questions & Answers

Setting up a private path

Hi all, This is probably a very simple question but I couldn't even think of how to phrase it intelligently so google could tell me the answer. Basically I am a user on a server, I am not the admin and do not have root privileges. I have downloaded a bunch of programs that I need to use and... (2 Replies)
Discussion started by: DavyK1984
2 Replies

7. UNIX for Dummies Questions & Answers

Is there any $PATH default setting?

This is a very newbie's question: I was trying to add a new version of the same command "blastn", but the old command always shows up first. which blastn /usr/local/bin/blastnThe two versions of the same command "blastn" are located in: which -a blastn /usr/local/bin/blastn... (5 Replies)
Discussion started by: yifangt
5 Replies

8. Shell Programming and Scripting

Setting class path

hi , can anybody help me to chage the class path in unix server.. what are the files need to update .... (2 Replies)
Discussion started by: Madhu Siddula
2 Replies

9. Programming

Gcc linker search path order

I have a build where I wish to link against and load a specific version of a library and a different version of the same library is installed on the system. I'm using a -L option to point to the version that I wish to link against but gcc still seems to choose the installed version. Is there a way... (4 Replies)
Discussion started by: Richard Johnson
4 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 01:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy