[issue18320] python installation is broken if prefix is overridden on an install target

Ned Deily added the comment: Allowing prefix to be overridden after configure-time is certainly not the most critical shortcoming of the Python build system and it is possible someone is relying on that behavior. Since no one, including me, seems very interested at this point in trying to cha

[issue18320] python installation is broken if prefix is overridden on an install target

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue18320] python installation is broken if prefix is overridden on an install target

Martin Panter added the comment: I agree with Martin v. Löwis that this is not a real bug. Cosmicduck doesn’t seem aware of the “configure --prefix=. . .” option, but I don’t think it is right to add hacks to the makefile to prevent overriding variables. -- nosy: +martin.panter __

[issue18320] python installation is broken if prefix is overridden on an install target

Ned Deily added the comment: cosmicduck, the recommended and supported way to do this is by specifying the installation prefix at the configure step, not at the "make install" step: ./configure --prefix=${HOME}/scripts/tools/python/python-3.3.2 make make install If done this way, the ins

[issue18320] python installation is broken if prefix is overridden on an install target

cosmicduck added the comment: Hi, this is a problem for all users which have to want to use python on there own home directory. I wonder me, how did some other projects could install python to different directories e.g. OpenCSW it did on /opt/csw/... My most problem is, that I can do many but

[issue18320] python installation is broken if prefix is overridden on an install target

Ned Deily added the comment: "Also, how many variables would you want to protect from being changed? People may come up with ideas of changing arbitrary other Makefile variables, and guarding all of them is just not feasible." I certainly wasn't contemplating guarding *all* of them. I'm conce

[issue18320] python installation is broken if prefix is overridden on an install target

Martin v. Löwis added the comment: -1 on adding such a test. Some people may rely on the current behaviour, and use that to put the installation into some intermediate location (although DESTDIR would be a better approach for that). Also, how many variables would you want to protect from being

[issue18320] python installation is broken if prefix is overridden on an install target

Ned Deily added the comment: The problem you see is being caused by trying to override "prefix" on the "altinstall" or "install" targets. While Makefiles for many products will let you do that successfully, you really can't do that with Python's. Unfortunately, the values for "prefix" and "e