Message 382928 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	pflagerd
Recipients	lemburg, pflagerd, vstinner
Date	2020年12月13日.03:04:12
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1607828652.34.0.490116162116.issue40505@roundup.psfhosted.org>

Content
Python-3.9.1 OpenSUSE 15.1 While ./configure --with-platlibdir=lib64 does work-around the problem on OpenSUSE by putting everything into lib64/, this is not the default behavior. In other words, should Python-3.9.1 be built on OpenSUSE 15.1 without --with-platlibdir=lib64, the behavior described in this bug report occurs. Not everyone building Python-3.9.1 on OpenSUSE will take the time to research this and end up finding https://bugs.python.org/issue1294959 (as I did after considerable effort). Intuitively, doesn't one expect configure to work this kind of thing out (and if it can't, warn the user)?

Content

Python-3.9.1 OpenSUSE 15.1
While ./configure --with-platlibdir=lib64 does work-around the problem on OpenSUSE by putting everything into lib64/, this is not the default behavior. In other words, should Python-3.9.1 be built on OpenSUSE 15.1 without --with-platlibdir=lib64, the behavior described in this bug report occurs.
Not everyone building Python-3.9.1 on OpenSUSE will take the time to research this and end up finding https://bugs.python.org/issue1294959 (as I did after considerable effort).
Intuitively, doesn't one expect configure to work this kind of thing out (and if it can't, warn the user)?

History
Date	User	Action	Args
2020年12月13日 03:04:12	pflagerd	set	recipients: + pflagerd, lemburg, vstinner
2020年12月13日 03:04:12	pflagerd	set	messageid: <1607828652.34.0.490116162116.issue40505@roundup.psfhosted.org>
2020年12月13日 03:04:12	pflagerd	link	issue40505 messages
2020年12月13日 03:04:12	pflagerd	create

homepage