Date: Tue, 28 Jun 2016 12:32:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 209526] devel/ncurses: Fix installed .pc file to use -Wl, -rpath rather than -rpath Message-ID: <bug-209526-13-ZCjkcq0Oq4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209526-13@https.bugs.freebsd.org/bugzilla/> References: <bug-209526-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209526 --- Comment #7 from John Hein <z7dr6ut7gs@snkmail.com> --- Upstream commit (slightly different arrangement than the patch in attachment 170328 but equivalent effect): http://lists.gnu.org/archive/html/bug-ncurses/2016-02/msg00009.html and http://lists.gnu.org/archive/html/bug-ncurses/2016-02/msg00006.html That is also mentioned in bug 178732 comment 14 (the discussion that spawned this bug) - that freebsd bug is mentioned in the upstream announcement. When 6.1 is released and the ncurses port is updated for 6.1, this patch ca= n be reverted. I can confirm that this passes various QA tests: portlint - no new errors due to patch [1] testport - passes (tested on 9-stable/i386) stage-qa - passes Triggering an exp-run is fine if you think this patch merits it. I've been running with this in a number of ports trees that get regular build updates= for 5+ months now - sort of an anecdotal partial exp-run. [1] Existing portlint nitpicks could be fixed by a motivated committer, but= are not relevant in the context of this PR. If possible, please address those after committing this fix. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209526-13-ZCjkcq0Oq4>