[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-06-11 Thread Tarek Ziadé
Tarek Ziadé ziade.ta...@gmail.com added the comment: done in r73341 in trunk. I've backported it as well in 2.6/3.0/3.1 branches. (r73342, r73343, r73344) Thanks ! -- status: open - closed ___ Python tracker rep...@bugs.python.org

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-06-10 Thread Floris Bruynooghe
Floris Bruynooghe floris.bruynoo...@gmail.com added the comment: Hi What's the status of this? I haven't seen a commit message regarding this. Cheers -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5201

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-05-26 Thread Tarek Ziadé
Tarek Ziadé ziade.ta...@gmail.com added the comment: The patch looks good, beside the fact that you didn't call super() in setUp/tearDown. I'll commit it asap and fix that small issue -- ___ Python tracker rep...@bugs.python.org

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-05-12 Thread Floris Bruynooghe
Floris Bruynooghe floris.bruynoo...@gmail.com added the comment: Oh, sorry about the super() that is why the ar test failed then. Sorry, I got a little confused by the conflicting update on that file while working on this patch and must have merged it badly. --

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-05-11 Thread Floris Bruynooghe
Floris Bruynooghe floris.bruynoo...@gmail.com added the comment: The updated patch inserts the single $ when needed. I've checked this on compiling python, stdlib extension modules and custom extension modules and this gives the correct results in all cases. -- Added file:

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-05-02 Thread Floris Bruynooghe
Floris Bruynooghe floris.bruynoo...@gmail.com added the comment: The attached patch does fix this issue. Concerning the specific example of LDFLAGS used here there is still and issue with LDFLAGS being ignored by the buid for the shared modules, but that is an other issue. -- keywords:

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-05-02 Thread Floris Bruynooghe
Floris Bruynooghe floris.bruynoo...@gmail.com added the comment: Hmm, the patch isn't quite right yet. When a $$ is present in the makefile .parse_makefile() needs to return a single $. I'm not sure yet what needs to happen with the \ for the shell escape. --

[issue5201] Using LDFLAGS='-rpath=\$$LIB:/some/other/path' ./configure breaks the build

2009-02-10 Thread Floris Bruynooghe
New submission from Floris Bruynooghe floris.bruynoo...@gmail.com: When specifying an RPATH with -rpath or -R you can use the special tokens `$LIB' and `$ORIGIN' which the runtime linker interprets as normal search path and relative to current sofile respectively. To get these correctly to the