From owner-freebsd-python@freebsd.org Fri Jul 13 09:18:42 2018 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D341210308EB for ; Fri, 13 Jul 2018 09:18:41 +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 906B57C9A6 for ; Fri, 13 Jul 2018 09:18:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5178610308E6; Fri, 13 Jul 2018 09:18:41 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F01410308E5 for ; Fri, 13 Jul 2018 09:18:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C23D37C9A3 for ; Fri, 13 Jul 2018 09:18:40 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0DE1AA770 for ; Fri, 13 Jul 2018 09:18:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6D9Idmo059597 for ; Fri, 13 Jul 2018 09:18:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6D9Id2d059588 for python@FreeBSD.org; Fri, 13 Jul 2018 09:18:39 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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 Date: Fri, 13 Jul 2018 09:18:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: tobik@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: 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.27 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2018 09:18:42 -0000 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.=