Prefer https for Sourceware links

Update all sourceware links to https.  The website redirects
everything to https anyway so let the web server do a bit less work.
The only reference that remains unchanged is the one in the old
ChangeLog, since it didn't seem worth changing it.

	* NEWS: Update sourceware link to https.
	* configure.ac: Likewise.
	* crypt/md5test-giant.c: Likewise.
	* dlfcn/bug-atexit1.c: Likewise.
	* dlfcn/bug-atexit2.c: Likewise.
	* localedata/README: Likewise.
	* malloc/tst-mallocfork.c: Likewise.
	* manual/install.texi: Likewise.
	* nptl/tst-pthread-getattr.c: Likewise.
	* stdio-common/tst-fgets.c: Likewise.
	* stdio-common/tst-fwrite.c: Likewise.
	* sunrpc/Makefile: Likewise.
	* sysdeps/arm/armv7/multiarch/memcpy_impl.S: Likewise.
	* wcsmbs/tst-mbrtowc2.c: Likewise.
	* configure: Regenerate.
	* INSTALL: Regenerate.

1 files changed, 2 insertions, 2 deletions

diff --git a/INSTALL b/INSTALL
index bc972b2ffa..35e82fbca9 100644
--- a/INSTALL
+++ b/INSTALL
@@ -2,7 +2,7 @@ Installing the GNU C Library
 ****************************
 
 Before you do anything else, you should read the FAQ at
-<http://sourceware.org/glibc/wiki/FAQ>.  It answers common questions and
+<https://sourceware.org/glibc/wiki/FAQ>.  It answers common questions and
 describes problems you may experience with compilation and installation.
 
    You will need recent versions of several GNU tools: definitely GCC
@@ -541,7 +541,7 @@ remain unfixed for all eternity, if not longer.
    It is a good idea to verify that the problem has not already been
 reported.  Bugs are documented in two places: The file 'BUGS' describes
 a number of well known bugs and the central GNU C Library bug tracking
-system has a WWW interface at <http://sourceware.org/bugzilla/>.  The
+system has a WWW interface at <https://sourceware.org/bugzilla/>.  The
 WWW interface gives you access to open and closed reports.  A closed
 report normally includes a patch or a hint on solving the problem.