[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2013-10-13 Thread Georg Brandl
Georg Brandl added the comment: Closing due to lack of feedback. -- nosy: +georg.brandl resolution: -> works for me status: pending -> closed ___ Python tracker ___

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-07-24 Thread Petri Lehtinen
Petri Lehtinen added the comment: ysj.ray: As you're on Debian, the real cause of this might be issue 11715. The Modules/Setup.dist line for zlib is commented out, so it's only an example of how to enable zlib if it's not found automatically. Can you try again now that issue 11715 has been f

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-15 Thread ysj.ray
ysj.ray added the comment: Isn’t zlib built by setup.py anyway? If can be build by Modules/Setup first as a builtin module, then the setup.py woun't build it. -- ___ Python tracker _

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-15 Thread R. David Murray
R. David Murray added the comment: I normally build using --prefix, often with --prefix=/dev/null, and I can't recall any version not building zlib. Of course, I don't uncomment the zlib entry in Modules/Setup. As far as I can see the zlib entry is unique in Setup in using prefix, so it pro

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-15 Thread Petri Lehtinen
Petri Lehtinen added the comment: FWIW, I recall that I built 2.7 a while back with --prefix=/home/user/something and it also failed to find zlib. Due to lack of time, I didn't debug it very deeply then, though. -- ___ Python tracker

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: Well, using $(prefix)/include to fetch development headers sounds like the wrong strategy anyway. Just because you e.g. install into /usr/local doesn't mean your zlib is inside /usr/local too. And if that makes people use our own zlib headers by mistake, then

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-13 Thread Petri Lehtinen
Changes by Petri Lehtinen : -- nosy: +petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-04 Thread Éric Araujo
Éric Araujo added the comment: Isn’t zlib built by setup.py anyway? -- nosy: +eric.araujo resolution: invalid -> status: pending -> open ___ Python tracker ___

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-06-01 Thread R. David Murray
R. David Murray added the comment: Well, IIUC the Setup lines indicate where to find the system version of the libraries (otherwise the included zlib is used). So I'm not at all sure that there is a bug here. If you change Setup, you need to change it correctly for your intended installatio

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-05-31 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- versions: -Python 2.5 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue11934] build with --prefix=/dev/null and zlib enabled in Modules/Setup failed

2011-04-27 Thread ysj.ray
New submission from ysj.ray : The development guide(http://docs.python.org/devguide/setup.html) suggested that one can build with "--prefix=/dev/null" in order to avoid accidentally install it. But in the Modules/Setup.dist the zlib module is defined as: zlib zlibmodule.c -I$(prefix)/include -