Mountain Lion Breaks Clamscan AV

Newbish · 07-25-2012, 05:06 PM

Hi, folks, I'm a little stuck and a little rusty.

Mountain Lion breaks clamscan, and using the command line ./configure results in the error: no acceptable C compiler found in $PATH.

I've never been able to get XCode to build anything to date, so I usually resorted to compiling on the command line. (Someday, someone will write a book, XCode for Dummies, that shows how to get XCode to build usable code with just one or two mouse clicks, instead of going through hours of garbage...)

Anyways <shoving soapbox to one side /> does anyone know where I can point clamscan's configure file so it can find the updated compiler in ML?

Newbish · 07-25-2012, 06:35 PM

A little update. Clamscan works fine on another computer after the Mountain Lion update, so I can only assume that something got munged on the one I'm wrestling with.

File it under the "Law of the Perversity of Machines"…

ganbustein · 07-25-2012, 08:16 PM

OS X does not install "development" tools like compilers and such by default. You need to install and run Xcode, go to Preferences→Downloads→Components, and install the command line tools.

Newbish · 07-25-2012, 08:28 PM

Quote:

Originally Posted by ganbustein


	OS X does not install "development" tools like compilers and such by default. You need to install and run Xcode, go to Preferences→Downloads→Components, and install the command line tools.

Yup. Already knew that.

Already installed.

But the "Download Components" is new to me. In the past, XCode always installed the command line components on installation. (I did say I was rusty)

I'll give it a whirl.

ganbustein · 07-25-2012, 08:49 PM

Installing a new OS would have completely replaced /bin, /sbin, and all of /usr except /usr/local. Any application-specific command line tools will have to be re-installed.

Check other things besides Xcode that may have installed command line tools. BBEdit, for example, installs /usr/bin/bbedit, /usr/bin/bbdiff, /usr/bin/bbfind, and their man pages. Thanks for reminding me to check if they need to be re-installed.

The reason Xcode doesn't install all that stuff automatically any more is to keep Xcode's download small. It used to take ages to download/update Xcode, partly because of all the baggage it always carried "just in case someone wanted it". Now you specifically ask for just the components you want.

Newbish · 07-25-2012, 08:52 PM

LOL! Yeah, I'm doing just that, checking BBEdit and a few other things.

The Xcode situation makes sense. It also may explain some of my recent failures at trying to got some things working properly. (I've been doing more writing than coding the past couple of years, so I've gotten very rusty on the tech side of things and stopped keeping up on all the changes.)

Newbish · 07-26-2012, 09:34 AM

Quote:

Originally Posted by ganbustein


	OS X does not install "development" tools like compilers and such by default. You need to install and run Xcode, go to Preferences→Downloads→Components, and install the command line tools.

That was absolutely the solution to the problem!

07-25-2012, 05:06 PM	#1
Newbish Triple-A Player Join Date: Nov 2002 Location: Massachusetts Posts: 202	Mountain Lion Breaks Clamscan AV Hi, folks, I'm a little stuck and a little rusty. Mountain Lion breaks clamscan, and using the command line ./configure results in the error: no acceptable C compiler found in $PATH. I've never been able to get XCode to build anything to date, so I usually resorted to compiling on the command line. (Someday, someone will write a book, XCode for Dummies, that shows how to get XCode to build usable code with just one or two mouse clicks, instead of going through hours of garbage...) Anyways <shoving soapbox to one side /> does anyone know where I can point clamscan's configure file so it can find the updated compiler in ML? __________________ There is no such thing as a stupid question. If you don't ask, you will never know.

07-25-2012, 06:35 PM	#2
Newbish Triple-A Player Join Date: Nov 2002 Location: Massachusetts Posts: 202	A little update. Clamscan works fine on another computer after the Mountain Lion update, so I can only assume that something got munged on the one I'm wrestling with. File it under the "Law of the Perversity of Machines"… __________________ There is no such thing as a stupid question. If you don't ask, you will never know.

07-25-2012, 08:52 PM	#6
Newbish Triple-A Player Join Date: Nov 2002 Location: Massachusetts Posts: 202	LOL! Yeah, I'm doing just that, checking BBEdit and a few other things. The Xcode situation makes sense. It also may explain some of my recent failures at trying to got some things working properly. (I've been doing more writing than coding the past couple of years, so I've gotten very rusty on the tech side of things and stopped keeping up on all the changes.) __________________ There is no such thing as a stupid question. If you don't ask, you will never know. Last edited by Newbish; 07-25-2012 at 08:55 PM.

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

07-25-2012, 08:16 PM	#3
ganbustein MVP Join Date: Apr 2008 Location: Berkeley CA USA Posts: 1,009	OS X does not install "development" tools like compilers and such by default. You need to install and run Xcode, go to Preferences→Downloads→Components, and install the command line tools.

07-25-2012, 08:49 PM	#5
ganbustein MVP Join Date: Apr 2008 Location: Berkeley CA USA Posts: 1,009	Installing a new OS would have completely replaced /bin, /sbin, and all of /usr except /usr/local. Any application-specific command line tools will have to be re-installed. Check other things besides Xcode that may have installed command line tools. BBEdit, for example, installs /usr/bin/bbedit, /usr/bin/bbdiff, /usr/bin/bbfind, and their man pages. Thanks for reminding me to check if they need to be re-installed. The reason Xcode doesn't install all that stuff automatically any more is to keep Xcode's download small. It used to take ages to download/update Xcode, partly because of all the baggage it always carried "just in case someone wanted it". Now you specifically ask for just the components you want.