Date: Fri, 13 Jul 2018 09:18:39 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 229749] lang/python36: python3.6-config breaks when symlinked e.g. by using BINARY_ALIAS in ports Message-ID: <bug-229749-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229749 Bug ID: 229749 Summary: lang/python36: python3.6-config breaks when symlinked e.g. by using BINARY_ALIAS in ports Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: python@FreeBSD.org Reporter: tobik@freebsd.org Flags: maintainer-feedback?(python@FreeBSD.org) Assignee: python@FreeBSD.org When using BINARY_ALIAS together with python3.6-config, i.e. symlinking it to another location, it starts outputting bogus paths. USES=3D python:3.6+ BINARY_ALIAS=3D python3-config=3Dpython${PYTHON_VER}-config It is convenient to use when porting applications that hardcode use of python3-config etc. It works fine with python2.7-config. However when I try a similar thing with python3.6-config it starts outputting bogus paths. For example $ pwd /home/tobias $ python2.7-config --includes -I/usr/local/include/python2.7 -I/usr/local/include/python2.7 $ ln -s /usr/local/bin/python2.7-config python2-config $ ./python2-config --includes -I/usr/local/include/python2.7 -I/usr/local/include/python2.7 $ python3.6-config --includes -I/usr/local/include/python3.6m -I/usr/local/include/python3.6m $ ln -s /usr/local/bin/python3.6-config python3-config $ ./python3-config --includes -I/home/include/python3.6m -I/home/include/python3.6m It would be nice if this could just work as it does with Python 2.7. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229749-21822>