From owner-freebsd-python@freebsd.org Mon Aug 28 05:12:02 2017 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B923E05BA8 for ; Mon, 28 Aug 2017 05:12:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 329336945B for ; Mon, 28 Aug 2017 05:12:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 31EE6E05BA7; Mon, 28 Aug 2017 05:12:02 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3196EE05BA6 for ; Mon, 28 Aug 2017 05:12:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17EC16945A for ; Mon, 28 Aug 2017 05:12:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7S5C1P8065491 for ; Mon, 28 Aug 2017 05:12:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 220332] lang/python27,33,34,35: "cc: error: unsupported option '-print-multi-os-directory'" Date: Mon, 28 Aug 2017 05:12:02 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 05:12:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220332 --- Comment #6 from Kubilay Kocak --- Tracing it back (scoping to gcc): Modules/_ctypes/libffi/configure.ac:=20 if test "x$GCC" =3D "xyes"; Python/configure: { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5 $as_echo "$ac_cv_c_compiler_gnu" >&6; } if test $ac_compiler_gnu =3D yes; then GCC=3Dyes else GCC=3D fi config.log: ... configure:4152: checking whether we are using the GNU C compiler configure:4171: cc -c -O2 -pipe -march=3Dsandybridge -fstack-protector-str= ong -fno-strict-aliasing -I/usr/local/include conftest.c >&5 configure:4171: $? =3D 0 configure:4180: result: yes ... ## ---------------- ## ## Cache variables. ## ## ---------------- ## ... ac_cv_c_compiler_gnu=3Dyes ... See also: AC_PROG_CC wrongly setting $GCC=3Dyes while clang is used https://lists.gnu.org/archive/html/autoconf/2014-09/msg00022.html This appears to explain why it is being run in the first place. However .. In Modules/_ctypes/libffi/configure: ... sourced from _ctypes/libffi/m4/libtool.m4 # Ok, now we have the path, separated by spaces, we can step through it # and add multilib dir if necessary... lt_tmp_lt_search_path_spec=3D lt_multi_os_dir=3D/`$CC $CPPFLAGS $CFLAGS $LDFLAGS -print-multi-os-direct= ory 2>/dev/null` # ...but if some path component already ends with the multilib dir we ass= ume # that all is fine and trust -print-search-dirs as is (GCC 4.2? or newer). case "$lt_multi_os_dir; $lt_search_path_spec " in "/; "* | "/.; "* | "/./; "* | *"$lt_multi_os_dir "* | *"$lt_multi_os_dir/= "*) lt_multi_os_dir=3D ;; esac ... sourced from ctypes/libffi/configure.ac multi_os_directory=3D`$CC $CFLAGS -print-multi-os-directory` case $multi_os_directory in .) ;; # Avoid trailing /. ../*) toolexeclibdir=3D$toolexeclibdir/$multi_os_directory ;; esac My current (potentially naive/incomplete/incorrect) reading of the code is = that it is (just) a compiler invocation in order to test for multilib support, or certain values from a compiler that supports that option, which would resul= t in the observed error output instead for any compiler that didn't (as expected= for clang?, being a NOOP?). The comment in Modules/_ctypes/libffi/m4/libtool.m4 # Ok, now we have the path, separated by spaces, we can step through it # and add multilib dir if necessary... That is, the 'if necessary part', appears to be an additional clue that its just a check, without impact if the expected results are not found. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=