Issue 5638: test_httpservers fails CGI tests if --enable-shared (original) (raw)

Issue5638

Created on 2009-04-01 03:11 by tony_nelson, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg84969 - (view)	Author: Tony Nelson (tony_nelson)	Date: 2009-04-01 03:11
test_httpservers fails the CGI tests if Python was built as a shared library (./config --enable-shared) and not yet installed. To run such a Python without installing it, the command line must define LD_LIBRARY_PATH to point to the build directory. I see that the new environment for the child CGI process still has LD_LIBRARY_PATH set. The child process is not using that when the CGI is invoked. After the new shared Python (or one like it) is installed, the test passes, but the CGIs aren't using the correct copy of Python. I'm doing this with Python 2.6.1, but the version probably doesn't matter.
msg109881 - (view)	Author: Mark Lawrence (BreamoreBoy) *	Date: 2010-07-10 15:38
Would anyone like to comment on this.
msg221799 - (view)	Author: Terry J. Reedy (terry.reedy) *	Date: 2014-06-28 16:03
David, Senthil, can either of you make any sense of this? Is the described configuration supported? Or should we close this?
msg221805 - (view)	Author: Ned Deily (ned.deily) *	Date: 2014-06-28 18:06
I don't see where any problems were fixed but I've verified that with current default that this case works correctly if you start the tests correctly as "make test" does. LD_LIBRARY_PATH=$CWD ./python -m test ... The cgi test cases create a temporary directory, set up a symlink for python using the value of sys.executable, which should be ./python, and the LD_LIBRARY_PATH environment variable (or equivalent on the platform) is inherited in the test cases. I suppose you could run into trouble *if* there already is a Python shared library installed in the prefix location and on the platform, directories in LD_LIBRARY_PATH are not searched first. If that's the case, then there's little Python can do and other tests would fail. In such a situation, you would either have to install first or, for test purposes, use a temporary value for --prefix when running configure and make a test-only build.