I have a clean FreeBSD 14.0-CURRENT installation. I have update ports (`portsnap fetch update`). I would like to install `py-cryptography` but when I run `make install` I get the following outotput: """ [...] ===> py37-cryptography-3.3.2 depends on package: py37-cffi>=1.8 - found ===> Returning to build of py37-cryptography-3.3.2 ===> py37-cryptography-3.3.2 depends on package: py37-setuptools>0 - found ===> py37-cryptography-3.3.2 depends on file: /usr/local/bin/python3.7 - found ===> Configuring for py37-cryptography-3.3.2 running config """ And then it does not continue. It is blocked after print `running config`.
Hi barroco, This is most likely because of commit d36d6816151705907393889 on 14.0-CURRENT. It has been discussed on ML for some days and should be fixed now with with https://freshbsd.org/freebsd/src/commit/7cb32a0d03437f881169b1c55cce89cf70ed43dd So all you have to do is updating your 14.0-CURRENT and rebuild/reinstall :) HTH, Rainer
Similar problem with FreeBSD-13 RC5. In this case, compilation ends with an error because `makeinfo` does not found. I think makeinfo is in textinfo package but I am not sure. But I can not found that package in FreeBSD repository. That compilation works fine with FreeBSD-12.2 version, so there is anything wrong in FreeBSD 13 RC5 and FreeBSD 14. Another comment about compilations of ports: compilation in FreeBSD 13 and FreeBSD 14 versions are very slower than FreeBSD 12. You can test with `nano` compilation.
(In reply to Rainer Hurling from comment #1) Sorry, I did not see your reply. I have the latest version of 14.0-CURRENT. I have download the ISO today and I have download ports today (fetch, extract, update). Do you think I am doing anything wrong? As well, s you can see in my comment #2 (2021-04-11 21:56:24 UTC), there is another problem with py-cryptografy with FreeBSD 13 RC5. Thank you for your reply.
Re: FreeBSD 14, that ISO is probably a bit out of date, so you either need to checkout a fresh main and buildworld/kernel to update it, or wait for a new ISO to be produced.
Please try reproducing this issue again. If you can repro the problem, please reopen the bug.