[issue16591] RUNSHARED wrong for OSX no framework

2021-09-10 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> many distutils tests fail when run from the installed location ___ Python tracker _

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Fabian Groffen
Fabian Groffen added the comment: > 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. -- ___ Python tracker

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Ronald Oussoren
Ronald Oussoren added the comment: On 31 Dec, 2012, at 15:59, Fabian Groffen 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

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Fabian Groffen
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

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Hynek Schlawack
Hynek Schlawack added the comment: I’m fine with that. My focus was fixing the ticket metadata. :) -- ___ Python tracker ___ ___ Pytho

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Ronald Oussoren
Ronald Oussoren added the comment: > Hynek Schlawack added the comment: > > $(pwd) 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. ---

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Hynek Schlawack
Hynek Schlawack added the comment: $(pwd) -- stage: -> patch review versions: +Python 3.4 ___ Python tracker ___ ___ Python-bugs-list

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-31 Thread Ronald Oussoren
Ronald Oussoren added the comment: 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) -- nosy: +

[issue16591] RUNSHARED wrong for OSX no framework

2012-12-01 Thread Fabian Groffen
New submission from Fabian Groffen: 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 r