[Distutils] trouble determining source for gcc command arguments

Ned Deily nad at acm.org
Sun Feb 5 10:36:41 CET 2012

In article 
<CAPVV--O+__Bg5MHBe5haq1BTGAZayC6NYKA9imxcXQ3kFv21Wg at mail.gmail.com>,
 Robert Altman <robert at altmansoftwaredesign.com> wrote:

> I have two mac os/x computers, each up to date with the same compiler
> and environments, yet it appears that distutils is emitting different
> gcc arguments.  Specifically, one of the computers is attempting to
> compile Mercurial using the -isysoot ... argument, effectively causing
> the build process to fail.
> Details: os/x 10.7
> Python 2.7.2 (installed from 10.7 installer at python.org)
> Mercurial source is 2.1
> I don't see any environment settings which would cause gcc to use to
> -isysroot argument and I cannot determine where else it might be
> coming from (it is not in the Mercurial project), so I believe it must
> be coming from distutils.

On OS/X, Distutils tries to ensure that any C extension modules it is 
asked to build are built with the same compiler options as Python itself 
was built with.  There is no particular reason why -sysroot should be a 
problem for building hg.  If you are seeing different results on the two 
machines with the same OS level and Pythons, most likely you aren't 
using the Pythons you think you are or you are setting environment 
variables to override the defaults.  In any case, you need to provide 
more information.  Exactly what errors are you seeing?

 Ned Deily,
 nad at acm.org

More information about the Distutils-SIG mailing list