Date: Tue, 05 Jul 2016 08:39:03 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 210837] lang/perl5.22 (and related?): ext/re/re_exec.c has long long format matched up with long argument Message-ID: <bug-210837-14331-2CHcp14FPF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210837-14331@https.bugs.freebsd.org/bugzilla/> References: <bug-210837-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=3D210837 --- Comment #2 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mathieu Arnold from comment #1) The problem may well need to be reported upstream and any fix in FreeBSD's port(s) may well wait on upstream updating. That is not for me to say. I did not build perl directly but it was involved via a dependency. (I build ports based on source.) I'm not familiar with perl's upstream at all. Your question told me more about upstream than I previously knew. "A list for people interested in Perl5 core development. High volume.": So = far I'm just reporting what the C/C++ compiler complained about and am not like= ly to be active on such a list. Looking around it appears that actual bug tracking is tied to: https://rt.perl.org/Public/ but as of yet I do not have an account there. There seems to be something called perlbug (see http://perldoc.perl.org/perlbug.html ). I'm not set up currently to try the latest stable release (apparently 5.24.0) but they request such testing. It= may be a while before I've done enough to make a reasonable upstream submittal. --=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-210837-14331-2CHcp14FPF>