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=" >> $FN
echo $0 $@ >> $FN
set >> $FN
gcc-real "$@"
echo "exitcode=$?" >> $FN
(I don't know if any of this will be different on OSX, I'm using Linux.)
Then run the command manually, and compare the dump files.
Here's hoping this helps,
Graham
On 10 Oct 2007, 12:36:13, Greg Ewing wrote:
> 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 setting it
> to 10.1, 10.2, 10.3, 10.4 and leaving it unset, and in
> all these cases the command works when run directly from
> the shell.
>
> So I'm not sure what to try next.
>
> --
> Greg
> ___
> Python-Dev mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/graham.horler%40gmail.com
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
