Date: Mon, 09 May 2016 21:46:43 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 209173] lang/perl5.22: port build has inappropriate use of -Wl, -R/usr/local/lib/perl5/5.22/mach/CORE before the update libperl.so.5.22.2 is there to use (11.0-CURRENT in use) Message-ID: <bug-209173-14331-uxs9OWDwfF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209173-14331@https.bugs.freebsd.org/bugzilla/> References: <bug-209173-14331@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=3D209173 --- Comment #5 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mark Millard from comment #4) This whole thing makes me wonder if the use of the staging step that ports builds use (a temporary place) simply violates the structure the perl installation materials are designed for. In other words: without using a staging area and directly installing under /usr/local/. . . during the install the kind of -Wl,-R/usr/local/lib/perl5/5.22/mach/CORE usage that I see in the logs would work. (Of course failed builds would then not have left the old install in place.) I'm not suggesting that staging be abandoned but any port with a tie such as this needs a more extensive adjustment to support staging, apparently inclu= ding the disabling/adjusting of the build code that reports its activity as: Adding -Wl,-R/usr/local/lib/perl5/5.22/mach/CORE to the flags passed to . .= . so that the perl executable will find the installed shared libperl.so.5.22.2 Or possibly linking for staging with a staging path in -Wl,-R , do the tests based on the staging area, then if they pass (re)linking with the final installation-path in -Wl,-R into staging and finally installing. (This would have its own risks.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209173-14331-uxs9OWDwfF>