On FreeBSD amd64 uname -p and uname -m report amd64. GNU config canonicalizes it as x86_64. Various upstream projects may not expect amd64 in configure target triple, so ports end up overriding CONFIGURE_TARGET. This may not be easily noticible if otherwise the build doesn't break e.g., x11/babl. Let's back out ports r319948 from *both* config.guess and config.sub. $ cd /path/to/config $ sh config.guess x86_64-unknown-freebsd11.0 $ sh config.sub amd64-unknown-freebsd11.0 x86_64-unknown-freebsd11.0 http://git.savannah.gnu.org/cgit/config.git/commit/?id=4e3da806cdd8 vs. $ cd /usr/ports $ sh Templates/config.guess amd64-unknown-freebsd11.0 $ sh Templates/config.sub amd64-portbld-freebsd11.0 amd64-portbld-freebsd11.0
Did portmgr time out itself? If there were replies off bugzilla those need to be linked here.
No, but there was no patch, and you did not ask for an exp-run. Feel free to re-open this and do so.
Re-open, clarifying summary. @Jan A patch (attachment) reverting r319948 may be more explicit for portmgr and potentially easier to exp-run for antoine
imho we should proceed with this change, Jan, will you provide a patch? if not I will do it in the next couple of days.
(In reply to Baptiste Daroussin from comment #4) > Resolution: --- → Overcome By Events Care to elaborate? I don't see any recent commits to Templates/config.guess, so FreeBSD Ports is still a special snowflake that requires s/x86_64/amd64/ in autotools-based projects. DragonFly and NetBSD don't require such patching on x86_64.
Sorry I messed up with another PR, anyway this will be covered by 266049