problems trying to install C compiler and software from source code
cybers...@hotmail.com
Compiler in the version of Linux that I have installed (Fedora 9). I
am having a problem trying to install the C Compiler from source code
and anyone's help would be greatly appreciated. I keep getting the
error message "no acceptable C Compiler found in $PATH" when I try and
run the executable configure file (./configure) from the tarball that
I have downloaded, uncompressed and extracted to my home directory.
Here are the steps that I've taken to troubleshoot.
Verified that I do not have a C compiler in any directory with the
command "which gcc."
Tried to install GNU C compiler with commands "update2 gcc" and/or
"yum install gcc."
downloaded the files http://cudlug.cudenver.edu/GNU/gnu/gcc/gcc-3.4.3/gcc-3.4.3.tar.bz2
and http://cudlug.cudenver.edu/GNU/gnu/gcc/gcc-3.4.3/gcc-core-3.4.3.tar.bz2
Uncompressed and extracted the files:tar xjvf gcc-g++-3.4.3.tar.bz2 ;
tar xjvf gcc-core-3.4.3.tar.bz2
Changed to the directory created after the download.
When I try and run the "./configure" file I receive the error response
again: "no acceptable C Compiler found in $PATH."
PLEASE HELP!
Andrew Kesterson
> and http://cudlug.cudenver.edu/GNU/gnu/gcc/gcc-3.4.3/gcc-core-3.4.3.tar.bz2
>
> Uncompressed and extracted the files:tar xjvf gcc-g++-3.4.3.tar.bz2 ;
> tar xjvf gcc-core-3.4.3.tar.bz2
>
> Changed to the directory created after the download.
>
> When I try and run the "./configure" file I receive the error response
> again: "no acceptable C Compiler found in $PATH."
GCC, ironically enough, is built by itself - that is to say, you have
to have GCC, in order to build GCC. Ever since the first GCC was built
with binutils (I think it was binutils - anyone around when the first
GCC was built, was it compiled with binutils or the 'cc' on a unix
box?), the previous version of GCC builds the next version, and so on.
So without a C compiler, you'll never be able to build GCC from source.
Anyways, skipping the history lesson, google is your friend.
It looks like fedora 9 ships with GCC 4.3 by default. What output did
your 'yum' commands give you? Do a 'locate gcc | grep bin' or 'find /
-name gcc', and one of those will definitely give you the location of
GCC if you actually have it. If those turn up a gcc binary somewhere,
then it's just an issue of setting your PATH to include that directory
('which' only looks inside of the $PATH environment variable, so if your
path is screwy, it'll break). If you indeed don't have gcc installed,
and yum (for whatever reason) refuses to work, you'll have to download a
binary gcc version from rpmfind.net. Just search for 'gcc' and install
what comes up for your version with 'rpm -ihv (rpm filenames)'. That
should get you up and running.
(FWIW, on a personal note, Fedora sucks balls. Ditch it for a real
distro like one of the Ubuntu flavors, and you'll be free of the
nightmare of RPM hunting.)
cyberseright
some downtime at work, I'm going to try everything you mentioned
pronto. As for Fedora, I am going to switch to a different
distribution pretty soon. I took a Linux + class about 5 months ago
and Fedora is the distribution that the instructor gave us to load in
class.
On Jan 26, 7:26 am, Andrew Kesterson <and...@aklabs.net> wrote:
> > downloaded the fileshttp://cudlug.cudenver.edu/GNU/gnu/gcc/gcc-3.4.3/gcc-3.4.3.tar.bz2
> > andhttp://cudlug.cudenver.edu/GNU/gnu/gcc/gcc-3.4.3/gcc-core-3.4.3.tar.bz2
> > Uncompressed and extracted the files:tar xjvf gcc-g++-3.4.3.tar.bz2 ;
> > tar xjvf gcc-core-3.4.3.tar.bz2
>
> > Changed to the directory created after the download.
>
> > When I try and run the "./configure" file I receive the error response
> > again: "no acceptable C Compiler found in $PATH."
>
> GCC, ironically enough, is built by itself - that is to say, you have
> to have GCC, in order to build GCC. Ever since the first GCC was built
> with binutils (I think it was binutils - anyone around when the first
> GCC was built, was it compiled with binutils or the 'cc' on a unix
> box?), the previous version of GCC builds the next version, and so on.
> So without a C compiler, you'll never be able to build GCC from source.
>
> Anyways, skipping the history lesson, google is your friend.
>
cyberseright
some downtime at work, I'm going to try everything you mentioned
pronto. As for Fedora, I am going to switch to a different
distribution pretty soon. I took a Linux + class about 5 months ago
and Fedora is the distribution that the instructor gave us to load in
class.
On Jan 26, 7:26 am, Andrew Kesterson <and...@aklabs.net> wrote:
> > downloaded the fileshttp://cudlug.cudenver.edu/GNU/gnu/gcc/gcc-3.4.3/gcc-3.4.3.tar.bz2
> > Uncompressed and extracted the files:tar xjvf gcc-g++-3.4.3.tar.bz2 ;
> > tar xjvf gcc-core-3.4.3.tar.bz2
>
> > Changed to the directory created after the download.
>
> > When I try and run the "./configure" file I receive the error response
> > again: "no acceptable C Compiler found in $PATH."
>
> GCC, ironically enough, is built by itself - that is to say, you have
> to have GCC, in order to build GCC. Ever since the first GCC was built
> with binutils (I think it was binutils - anyone around when the first
> GCC was built, was it compiled with binutils or the 'cc' on a unix
> box?), the previous version of GCC builds the next version, and so on.
> So without a C compiler, you'll never be able to build GCC from source.
>
> Anyways, skipping the history lesson, google is your friend.
>