Python fails to run python.exe on OSX when a non-framework build is requested, due to wrong quoting in configure.ac.

Like all other RUNSHARED, it shouldn't be quoted because then `pwd` won't be expanded, resulting in a wrong DYLD_LIBRARY_PATH when regen is ran (from a different directory than where libpython3.3.dylib resides).

Attached patch solves the issue.  The issue seems to be in current 3.3 and default heads.

The patch can cause problems when either DYLD_LIBRARY_PATH or the current working directory contains whitepace, a better fix is:

RUNSHARED=DYLD_LIBRARY_PATH="`pwd`:${DYLD_LIBRARY_PATH}"

(That is, replace the single quotes by double quotes)

<bikeshed>$(pwd)</bikeshed>

> Hynek Schlawack added the comment:
> 
> <bikeshed>$(pwd)</bikeshed>

I'd usually agree, but this is a configure script and those shouldn't contain shell features invented after 1970 :-)

More seriously, a large subset of command interpolations in configure.ac use backticks.

I’m fine with that. My focus was fixing the ticket metadata. :)

re: single quotes -> double quotes

I made RUNSHARED consistent (although, as you point out, less broken) with the other RUNSHARED assignments right above.  If suggest to tackle the issue of whitespace support for all RUNSHARED assignments, not just Darwin case.

re: `pwd` vs. $(pwd)

$ /bin/sh
$ echo $(pwd)
syntax error: `(' unexpected

Here again, even though Darwin/OSX may be shipped with /bin/sh being bash (hence above problem not existing), for consistency, using `pwd` in all RUNSHARED assignments is nice, IMO.

On 31 Dec, 2012, at 15:59, Fabian Groffen <report@bugs.python.org> wrote:

> 
> Fabian Groffen added the comment:
> 
> re: single quotes -> double quotes
> 
> I made RUNSHARED consistent (although, as you point out, less broken) with the other RUNSHARED assignments right above.  If suggest to tackle the issue of whitespace support for all RUNSHARED assignments, not just Darwin case.

Maybe, but whitespace supporrt on OSX is more pressing than on regular Unix systems because users are more likely to create directory names with whitespace in them. 

> 
> re: `pwd` vs. $(pwd)
> 
> $ /bin/sh
> $ echo $(pwd)
> syntax error: `(' unexpected
> 
> Here again, even though Darwin/OSX may be shipped with /bin/sh being bash (hence above problem not existing), for consistency, using `pwd` in all RUNSHARED assignments is nice, IMO.

Which shell doesn't have $(command) support?  It is not a bash-ism, but is part of the POSIX shell definition (but wasn't present in older sh implementations).

> Which shell doesn't have $(command) support?  It is not a bash-ism, but
> is part of the POSIX shell definition (but wasn't present in older sh 
> implementations).

Solaris' /bin/sh.