Bugzilla Automation <bugzi...@freebsd.org> has asked freebsd-python mailing
list <pyt...@freebsd.org> for maintainer-feedback:
Bug 229749: lang/python36: python3.6-config breaks when symlinked e.g. by using
BINARY_ALIAS in ports
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229749
--- Description ---
When using BINARY_ALIAS together with python3.6-config, i.e. symlinking
it to another location, it starts outputting bogus paths.
USES= python:3.6+
BINARY_ALIAS= python3-config=python${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.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
