[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Building Subversion 1.2 on OS X 10.4 fails

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-12 05:10:12 CEST

On May 11, 2005, at 9:52 PM, Scott Palmer wrote:
> To be honest I find the entire process of "./configure" utterly
> ridiculous.

Perhaps you don't remember what the world was like before autoconf
existed? Eek.

> For example: It checks for things like stdlib.h - if you have a C
> compiler that doesn't have this file you have much bigger problems
> than compiling subversion. It checks for fortran compilers - why?
> subversion is written in C. I could go on, but the point is that
> the massive amount of "checking" just goes to show that there is
> something so fundamentally wrong with the entire process that it
> just makes me sad.

Fundamentally wrong? autoconf solves the problem of portability
better than anyone could have possibly dreamed of 20 years ago.
There's a reason it's the "standard'. Is it pleasant? No. Does it
greet you in the morning with french toast, the daily paper, and a
smile? No. Does it alleviate tremendous portability pain? Absolutely.

The behavior you're seeing is simply a bunch of pre-packaged tests
that are par for the course, part of the standard AC macros.
Subversion doesn't care about stdlib or fortran, it just asks that a
C compiler and preprocessor be present:

(from configure.in:)

dnl Look for a C compiler (before anything can set CFLAGS)

dnl Look for a C pre-processor

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 12 05:13:58 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.