Apple

On Apr 1, 2012, at 7:34 PM, Joe Hodge wrote:

I ran into the problem of missing "autoconf" while trying to install the latest Ruby and Python as I wanted to see if they where appropriate for a translation program I wanted to do. And yes, I feel constrained when given no other up-to-date programming languages other than the "C family". I started my first major app on a Lisa booting the Mac OS from disk back in the '80s writing in modula-2. I would like to try Eiffel since reading what's-his-name's book on it years ago when C was the "only language acceptable" for large projects. lol! I don't like to see innovation stifled on the Mac.

On Tue, Mar 27, 2012 at 16:53, Rick Mann <email@hidden> wrote:
On Mar 27, 2012, at 13:48 , Joar Wingfors wrote:
It depends on what you mean with the "GNU tool chain". That said, it's correct that autoconf/automake was dropped from the Xcode distribution starting with Xcode 4.3.

I'd argue that this is a bad move. Why did Apple do this? It's a real PITA to have to install a bunch of GNU tools to let open source projects build.

Out of curiosity, what projects require you to install
autoconf/automake just to build? Most ship autoconfiscated tarballs
that don't require the tools to be installed just for building. Many
require the tools available to hack on the projects, but they often
require specific versions of the tools that are generally newer than
what Apple was shipping anyway, so the apple-shipped versions didn't
relieve the need to install them and actually made things more
challenging in some cases.
I deal with a fair few autotools-driven projects, and I can't say I'm
even a little sorry to see them go from Xcode installations. Can you
link to a problem project?
Geoff

References:
	>Missing GNU tools -- who needs em'? (From: Joe Hodge <email@hidden>)