configure: error: no acceptable C compiler found in $PATH

Hi there,

I am trying to instal MD5deep from the terminal and get this error.
I have Xcode installed, which I think has a C compiler.
How con I point the instal ./config file to see an acceptable compiler?
Or is there some other way to do this?
Thanks!

Xcode should have set everything up properly when it was installed including symlinks. It's possible that something went wrong during the install - some people around here have had issues with GCC not being found. If you execute the following command, what does it print back?

gcc: Command not found.

log file....


checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... no
checking for style of include used by make... none
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/md5deep-3.9.1':
configure: error: no acceptable C compiler found in $PATH

GCC then is either not installed or is not in your PATH. The simple solution would be to reinstall XCode unless you want to take a look and see if it actually was installed. Take a look in /Developer/usr/bin and check to see if there is a version of gcc installed there. If it is in fact there (the binary will be named gcc-X.X where X.X is the version number), you can quickly symlink it to /usr/bin:

just reinstalled XCode...ran this...


gcc ==version
i686-apple-darwin9-gcc-4.0.1: ==version: No such file or directory
i686-apple-darwin9-gcc-4.0.1: no input files

gonna try the MD5deep config again

It's two dashes, not equal signs. That said, it looks as if GCC is installed and ready to go.

well...it looks like it loaded...but get errors when I try to use it...
trying to do what they say on their website -

Computing hashes

By default, md5deep generates MD5 hashes for each input file, displaying the full path information for each file:
$ md5deep config.h INSTALL README
b08b18e0a3d2440feb0b321ea8080b36 /home/jessek/coreutils-5.2.0/config.h
9f3e20fdff9c78aa8e3f9b42be166769 /home/jessek/coreutils-5.2.0/INSTALL
4aa18483f73fc56c907f0ae9025e2582 /home/jessek/coreutils-5.2.0/README


i get

[mymachine:~] user% md5deep config.h INSTALL README
md5deep: Command not found.
[mymachine:/md5deep-3.9.1] user% /md5deep-3.9.1/md5deep config.h INSTALL README
/md5deep-3.9.1/md5deep: Permission denied.
[mymachine:/md5deep-3.9.1] user% sudo /md5deep-3.9.1/md5deep config.h INSTALL README
Password:
sudo: /md5deep-3.9.1/md5deep: command not found
[mymachiner:/md5deep-3.9.1] user% config.h INSTALL
config.h: Command not found.

these are the only "no"s during the install


checking for gawk... no
checking for mawk... no
checking for nawk... no
checking whether we are cross compiling... no

checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no

checking whether byte ordering is bigendian... no
checking whether closedir returns void... no
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether gcc needs -traditional... no
checking whether lstat correctly handles trailing slash... no
checking whether lstat accepts an empty string... no
checking whether lstat correctly handles trailing slash... (cached) no
checking whether stat accepts an empty string... no
checking for _doprnt... no

md5deep should be a command right?
its really a folder

this is what I am using as guide

Getting Started with md5deep

Might I suggest that you use something like MacPorts. Once you have that installed, all you have to do is execute the following to update the ports: and install md5deep: That will download it and install it along with the dependencies.

thanks...trying that now...

can you tell me why I need to do that?
just curious why this is soooo incredibly difficult!

Thank you for all of your help too....

well...this sucks...


[mymachine:~] user% sudo port sync
sudo: port: command not found

[mymachine:~] user% sudo port install md5deep
sudo: port: command not found

well...finally some good news....but not enough...

[mymachine:~] user% sudo port install md5deep
---> Fetching md5deep
---> Attempting to fetch md5deep-3.9.1.tar.gz from md5deep and hashdeep - Browse Files at SourceForge.net
---> Verifying checksum(s) for md5deep
---> Extracting md5deep
---> Configuring md5deep
---> Building md5deep
---> Staging md5deep into destroot
---> Installing md5deep @3.9.1_0
---> Activating md5deep @3.9.1_0
---> Cleaning md5deep

[mymachine:~] user% md5deep config.h INSTALL README
md5deep: Command not found.

Why do they say to use this line of code if md5deep is not a command?

What else could be going on here?
This really is sucking.....

thanks again...just can't see why the docs are so careless....

zdvdla said:

thanks...trying that now...

can you tell me why I need to do that?
just curious why this is soooo incredibly difficult!

Thank you for all of your help too....

Click to expand...

Compiling code by hand can be tricky since you have to have all the right dependencies and tools installed. This is where something like MacPorts is nice since it takes care of all of it for you.

zdvdla said:

well...finally some good news....but not enough...

[mymachine:~] user% sudo port install md5deep
---> Fetching md5deep
---> Attempting to fetch md5deep-3.9.1.tar.gz from md5deep and hashdeep - Browse Files at SourceForge.net
---> Verifying checksum(s) for md5deep
---> Extracting md5deep
---> Configuring md5deep
---> Building md5deep
---> Staging md5deep into destroot
---> Installing md5deep @3.9.1_0
---> Activating md5deep @3.9.1_0
---> Cleaning md5deep

[mymachine:~] user% md5deep config.h INSTALL README
md5deep: Command not found.

Why do they say to use this line of code if md5deep is not a command?

What else could be going on here?
This really is sucking.....

thanks again...just can't see why the docs are so careless....

Click to expand...

Since MacPorts didn't print back any errors, the compilation was a success. If I remember correctly, MacPorts installs the apps to /opt and adds that path to your PATH (don't use MacPorts here anymore). What are the contents of your ~/.bash_profile and is there anything in /opt?

Hints from the Developer

Hi zdvdla,

This is Jesse Kornblum, the developer of md5deep.

zdvdla, I got your email, but replies to your SourceForge account bounced.

I'm sorry you're having trouble getting md5deep installed. You appear to be new to compiling software and using MacPorts. You should check that the Postflight script ran correctly (MacPorts Guide) You may also need to close out your Terminal window and open a new one to load the new configuration settings.

Here's what to try:

1. Quit the Terminal program

2. Restart the Terminal program

3. Try the md5deep command again. If it works, you're finished.

4. If you get an error message, run these commands and send me the results:

A listing of your home directory:
$ ls -a ~/

The contents of your PATH variable:
$ echo $PATH

Hope this helps,

Oh oh - I failed to look at second page of posts...
Van and Jesse covered just what I was going to.
So, you see, knowing what your PATH variable is is what we think is the key.
You will probably just want to put a symbolic link in /usr/local/bin. Read about that with "man ln." (small LN = ln for link)

You shouldn't need to symlink anything with MacPorts as the installer takes the path it installs applications to and adds it to the bash profile. I suspect Jesse in right in suggesting that the bash profile hasn't been re-read. The simple way to fix this is to simply restart Terminal.

Yup - you're right.