hi
From: Thomas Widlundh [mailto:tw@ettnet.se] Hi, I'm trying to install a tarball. It showed up that the gcc was missing. I installed it from the CD. Now a message: gcc was installed in /opt/experimental and I'm urged to put /opt/experimantal/bin in the path.
apparently you installed gcc 3.0, which is still considered experimental by suse.
Man path/PATH gave nothing. How do I put things in the path? Anybody knows?
PATH is an environment variable. what shell are you using? if you use csh or tcsh you can set your path with set PATH $PATH:/opt/experimental/bin if you use bash try export PATH=$PATH:/opt/experimental/bin for further information search google for "linux shell environment variables" :)
Thanks, Thomas
regards, stefan
Peer Stefan wrote:
Thomas Widlundh wrote:
How do I put things in the path?
PATH is an environment variable. what shell are you using? if you use csh or tcsh you can set your path with set PATH $PATH:/opt/experimental/bin if you use bash try export PATH=$PATH:/opt/experimental/bin
Then to make it permanent put this last line in ~/.bashrc. Another method: ln -s /opt/experimental/bin/gcc /opt/gcc Yet another method: copy this 2-line script into a file and store in in /usr/local/bin, naming it gcc. #! /bin/bash /opt/experimental/bin/gcc SH
Peer Stefan
apparently you installed gcc 3.0, which is still considered experimental by suse.
At the time 8.0 was created, gcc3 indeed had too many problems. Philipp -- Philipp Thomas work: pthomas@suse.de Development SuSE Linux AG private: philippt@t-online.de
Even gcc 3.1 has troubles. Try to compile a ocmplicated program with C++ and debug information in it and then do objdump -g xxxx You will get an error something like "bad mangled name". Talk to objdump (binutils) guys and they will tell you its a gcc bug not a binutils bug. Thats the reason I bought SuSE. It came with the last good version of gcc (2.95.3). Even 2.96 has its own set of problems. Salman On Wednesday 31 July 2002 03:18, Philipp Thomas wrote:
Peer Stefan
[ Wed, 24 Jul 2002 14:21:13 +0200]: apparently you installed gcc 3.0, which is still considered experimental by suse.
At the time 8.0 was created, gcc3 indeed had too many problems.
Philipp
Salman Khilji wrote:
Even gcc 3.1 has troubles. Try to compile a ocmplicated program with C++ and debug information in it and then do
objdump -g xxxx
You will get an error something like "bad mangled name".
Talk to objdump (binutils) guys and they will tell you its a gcc bug not a binutils bug.
Thats the reason I bought SuSE. It came with the last good version of gcc (2.95.3). Even 2.96 has its own set of problems.
2.96 was never meant to be a release. It was a beta release meant to be only a step between 2.95 and the next official 3.x release. We stick to 2.95.3 because it is THE official stable gnu compiler right now. We'll use 3.1 as default once it works for everything, meaning we can build the entire distribution with it - fro quality reasons we cannot build some packages with one compiler and others with another one! I *think* (I'm not involved in development) we'll be using it for 8.1. Michael
participants (5)
-
Michael Hasenstein
-
Peer Stefan
-
Philipp Thomas
-
Salman Khilji
-
Sjoerd Hiemstra