I wrote:
> As far as I can tell, it's using my PATH to find gcc,
> and that leads to /usr/bin/gcc, which is the same one
> my wrapper calls.
To make sure, I installed my wrapper in place of /usr/bin/gcc
and the same behaviour occurs.
--
Greg
___
Python
Oleg Broytmann wrote:
>Do you have a few different copies of gcc installed with setup.py called
> the wrong one and your shell script the right one?
As far as I can tell, it's using my PATH to find gcc,
and that leads to /usr/bin/gcc, which is the same one
my wrapper calls.
--
Greg
__
On Fri, Oct 12, 2007 at 09:21:15PM +1300, Greg Ewing wrote:
> So the bizarre state of affairs is that if distutils
> runs gcc through a shell script, it works, but if
> it runs gcc directly, it doesn't work.
>
> Anyone have any ideas on how that can happen?
Do you have a few different copies o
Graham Horler wrote:
> I would be inclined to move gcc to gcc-real (for example), and create a script
> called gcc which dumps all environment variables, and command-line arguments
Well, I tried that -- and things got even weirder still.
With the wrapper in place between distutils and gcc, the
li
I would be inclined to move gcc to gcc-real (for example), and create a script
called gcc which dumps all environment variables, and command-line arguments
and a time-stamp to /tmp/gcc., e.g.:
#!/bin/sh
FN=/tmp/gcc.$$
echo -n "date=" > $FN
date '+%Y/%m/%d %H:%M:%S.%N' >> $FN
echo -n "cmdline=" >>
Ronald Oussoren wrote:
> The deployment target does have an influence on how the compiler
> functions, which can explain when setting the target to a different
> value causes problems.
I did some more experimenting, and it doesn't seem to be
related to MACOSX_DEPLOYMENT TARGET. I tried settin
On 9 Oct, 2007, at 23:11, Greg Ewing wrote:
Ronald Oussoren wrote:
Is that the system supplied version of Python?
No, it's my own installation of 2.3, but it's installed
as a framework in /Library/Frameworks.
My guess is MACOSX_DEPLOYMENT_TARGET: this is set in the
> environment by distut
Ronald Oussoren wrote:
> Is that the system supplied version of Python?
No, it's my own installation of 2.3, but it's installed
as a framework in /Library/Frameworks.
> My guess is MACOSX_DEPLOYMENT_TARGET: this is set in the
> environment by distutils.
I wondered about that -- I've noticed th
On Tuesday, October 09, 2007, at 12:29PM, "Greg Ewing" <[EMAIL PROTECTED]>
wrote:
>A while back I wrote about a problem I was having with
>the ordering of -framework options in distutils compilation
>commands. Well, now I've discovered something even stranger.
>
>When distutils executes the foll
