Date: Wed, 23 Mar 2016 19:44:29 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 205600] arm's lang/perl5.20: via pkg install perl5: cc => '/nxb-bin/usr/bin/cc' in /usr/local/lib/perl5/5.20/mach/Config.pm Message-ID: <bug-205600-14331-LGT9aeru6E@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205600-14331@https.bugs.freebsd.org/bugzilla/> References: <bug-205600-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=3D205600 --- Comment #5 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mathieu Arnold from comment #4) Okay. At least I found the one type of problem in the patches. Unless I first had built perl5.xx while "${CC} =3D=3D /nxb-bin/usr/bin/cc" = was true any attempt at test-building devel/p5-Locale-gettext would not be based on = the new post-build target having been used during the perl5.xx build. In other words: It would not have tested your change if CC had any other pa= th (or was undefined) during the perl5.xx build. So I was looking for a valid (but temporary) way of allowing "${CC} =3D=3D /nxb-bin/usr/bin/cc" to be true during the perl5.xx build but not during the later devel/p5-Locale-gettext build. (This would simulate the conditions fr= om my original report but with post-build used for perl5.xx.) --=20 You are receiving this mail because: 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-205600-14331-LGT9aeru6E>