Skip to content

Commit 97fa06d

Browse files
rwp0khwilliamson
authored andcommitted
Replace FreeBSD URL's with new HTTPS ones
1 parent 80474df commit 97fa06d

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

README.freebsd

+2-2
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ When perl is configured to use ithreads, it will use re-entrant library calls
1919
in preference to non-re-entrant versions. There is a bug in FreeBSD's
2020
C<readdir_r> function in versions 4.5 and earlier that can cause a SEGV when
2121
reading large directories. A patch for FreeBSD libc is available
22-
(see L<http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/30631> )
22+
(see L<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=30631>)
2323
which has been integrated into FreeBSD 4.6.
2424

2525
=head2 C<$^X> doesn't always contain a full path in FreeBSD
@@ -29,7 +29,7 @@ system. On FreeBSD the full path of the perl interpreter is found by using
2929
C<sysctl> with C<KERN_PROC_PATHNAME> if that is supported, else by reading
3030
the symlink F</proc/curproc/file>. FreeBSD 7 and earlier has a bug where
3131
either approach sometimes returns an incorrect value
32-
(see L<http://www.freebsd.org/cgi/query-pr.cgi?pr=35703> ).
32+
(see L<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=35703>).
3333
In these cases perl will fall back to the old behaviour of using C's
3434
C<argv[0]> value for C<$^X>.
3535

caretx.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ Perl_set_caret_X(pTHX) {
121121
returning the text "unknown" from the readlink rather than the path
122122
to the executable (or returning an error from the readlink). Any
123123
valid path has a '/' in it somewhere, so use that to validate the
124-
result. See http://www.freebsd.org/cgi/query-pr.cgi?pr=35703
124+
result. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=35703
125125
*/
126126
if (len > 0 && memchr(buf, '/', len)) {
127127
sv_setpvn(caret_x, buf, len);

0 commit comments

Comments
 (0)