-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 27 April 2004 04:01 pm, you wrote:
> > configure: error: no acceptable C compiler found in $PATH
> > See `config.log' for more details.
>
> The error messages report that you had no C compiler installed that it
> could use in the authorized path. You need to install a C compiler or add
> the directory the c compiler is intalled into your path. The Gnu C compiler
> (gcc) would work.
> Smitty
In case you are wondering how to add to your path in Linux:
type
$ which gcc
you will likely get
$ /usr/bin/gcc
or something very similar.
If so, you can set the $PATH variable to include the path to gcc by typing
set PATH=$PATH:/usr/bin/
This appends the path /usr/bin/gcc to the end of whatever might have already
been in your $PATH variable.
Normally, /usr/bin would have been made a part of your path during the
installation of the operating system. If gcc isn't there, there is a very
real chance that you don't own it yet. If not, track it down either online or
on your distribution CD's and install it. You'll likely need it over and
over.
To see the complete set of environmental variables (available to any program
you might happen to run), type
$ set
Once you are certain that gcc is installed and that the the PATH variable has
been set to include the path to gcc, try ./configure / make / make install
again. You should get different results. When it works (pretty nearly always)
it's a thing of beauty. When it doesn't, it's a spiked speed bump in the
highway of life. Find ways around it ... in Linux there nearly always exists
at least 3 or 4 ways of accomplishing the same goal.
To see JUST the $PATH variable, type
$ set | grep PATH
This passes (pipes) the output of the set command through grep. Grep will
print any lines containing the desired text string (in this case, PATH) to
the screen.
I'm not certain, but I don't think "set PATH=$PATH:/usr/bin/gcc" results in a
permanent change to your path. If things go golly-wonkles, you could (here
come the flames now) reboot. Or, if you wisely kept a copy of the existing
PATH (set | grep PATH > oldpath.bak), you could keep trying until you figured
out how to set the $PATH properly.
It is possible you might not have gcc or anything like it installed. Look to
your distro media or google for it. A command closely related to 'which' that
you might want to experiment with is 'find'. Look at the man page for find
$ man find
Not certain that you needed any of this, but your original post looked like
you might be fairly new to Linux and probably unfamiliar with how to do what
Smitty said to do, which is, by the way, the right thing to do.
Bill
- --
http://cannaday.us (genealogy)
http://organic-earth.com (organic gardening)
Uptimes below for the machines that created / host these sites.
20:40:00 up 13 days, 4:25, 5 users, load average: 0.16, 0.28, 0.22
20:34:00 up 113 days, 23:46, 1 user, load average: 0.00, 0.00, 0.00
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAjwZqSvjcx4uv21sRAgfXAJ99SWO4osvHCxf2EaHP+yDuhHlLtACfduI0
pj6CTvHSJA4yQdBsv4WZ9ag=
=5S8p
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:26:00 EDT