From ab7203c1d6c80c5f37aeb8a0c4a59adc55093e70 Mon Sep 17 00:00:00 2001 From: "Jan (janneke) Nieuwenhuizen" Date: Sun, 30 Oct 2022 09:40:40 +0100 Subject: [PATCH] doc: Use HTTPS. * COPYING: Replace by new version (which uses HTTPS). * HACKING, README, doc/fdl-1.3.texi, doc/mes.texi: Use HTTPS. --- COPYING | 8 ++++---- HACKING | 32 ++++++++++++++++---------------- README | 6 +++--- doc/fdl-1.3.texi | 4 ++-- doc/mes.texi | 20 ++++++++++---------- 5 files changed, 35 insertions(+), 35 deletions(-) diff --git a/COPYING b/COPYING index 94a9ed02..f288702d 100644 --- a/COPYING +++ b/COPYING @@ -1,7 +1,7 @@ GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 - Copyright (C) 2007 Free Software Foundation, Inc. + Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -645,7 +645,7 @@ the "copyright" line and a pointer to where the full notice is found. GNU General Public License for more details. You should have received a copy of the GNU General Public License - along with this program. If not, see . + along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. @@ -664,11 +664,11 @@ might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see -. +. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read -. +. diff --git a/HACKING b/HACKING index b1fa7f37..4b1fedaf 100644 --- a/HACKING +++ b/HACKING @@ -130,30 +130,30 @@ x/s *((char **)($rsp+8)) ** C parser/compiler *** [[https://savannah.gnu.org/projects/nyacc][nyacc]] -*** PEG: [[http://piumarta.com/software/peg/][parse C using PEG]] +*** PEG: [[https://piumarta.com/software/peg/][parse C using PEG]] *** [[https://en.wikipedia.org/wiki/Tiny_C_Compiler][Tiny C Compiler]] -*** [[http://www.t3x.org/subc/index.html][Sub C]] +*** [[https://www.t3x.org/subc/index.html][Sub C]] *** [[https://groups.google.com/forum/#!topic/comp.lang.lisp/VPuX0VsjTTE][C intepreter in LISP/Scheme/Python]] ** C assembler/linker -*** [[http://www.tldp.org/HOWTO/Assembly-HOWTO/linux.html][Assembly HOWTO]] +*** [[https://www.tldp.org/HOWTO/Assembly-HOWTO/linux.html][Assembly HOWTO]] *** ELF 7f 45 4c 46 -*** [[http://www.muppetlabs.com/~breadbox/software/tiny/][Small ELF programs]] -*** [[http://www.cirosantilli.com/elf-hello-world/][Elf hello world]] +*** [[https://www.muppetlabs.com/~breadbox/software/tiny/][Small ELF programs]] +*** [[https://www.cirosantilli.com/elf-hello-world/][Elf hello world]] ** SC - c as s-expressions -sc: http://sph.mn/content/3d3 +sc: https://sph.mn/content/3d3 ** RNRS -*** [[http://www.scheme-reports.org/][Scheme Reports]] +*** [[https://www.scheme-reports.org/][Scheme Reports]] *** [[ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-349.pdf][Scheme - Report on Scheme]] *** [[ftp://publications.ai.mit.edu/ai-publications/pdf/AIM-452.pdf][RRS - Revised Report on Scheme]] ** tiny schemes -http://forum.osdev.org/viewtopic.php?f=15&t=19937 +https://forum.osdev.org/viewtopic.php?f=15&t=19937 -http://www.stripedgazelle.org/joey/dreamos.html -http://armpit.sourceforge.net/ -http://common-lisp.net/project/movitz/movitz.html +https://www.stripedgazelle.org/joey/dreamos.html +https://armpit.sourceforge.net/ +https://common-lisp.net/project/movitz/movitz.html janneke: https://github.com/namin/inc looks interesting [15:18] ** Orians Jeremiah @@ -170,13 +170,13 @@ http://common-lisp.net/project/movitz/movitz.html OriansJ: i looked a few times and saw 'LISP empty', so thanks for the pointer! [00:24] OriansJ, janneke: from that page, there's also: - https://web.archive.org/web/20160604035203fw_/http://homepage.ntlworld.com/edmund.grimley-evans/bcompiler.html + https://web.archive.org/web/20160604035203fw_/https://homepage.ntlworld.com/edmund.grimley-evans/bcompiler.html ** C4/C500 -https://web.archive.org/web/20160604041431/http://homepage.ntlworld.com/edmund.grimley-evans/cc500/cc500.c +https://web.archive.org/web/20160604041431/https://homepage.ntlworld.com/edmund.grimley-evans/cc500/cc500.c https://github.com/rswier/c4/blob/master/c4.c ** Compilers for free -http://codon.com/compilers-for-free +https://codon.com/compilers-for-free ** Small lisps *** [[https://www.mirrorservice.org/sites/www.bitsavers.org/bits/TI/Explorer/zeta-c/][ZETA-C]] ** Small C compilers @@ -188,10 +188,10 @@ simple as possible. *** pcc *** early GCC? https://miyuki.github.io/2017/10/04/gcc-archaeology-1.html -*** [[http://tack.sourceforge.net/][ack]] +*** [[https://tack.sourceforge.net/][ack]] it may be possible to compile like this: mes |> ack |> pcc |> tcc |> gcc 4.7.4 |> gcc later version... up to modern -*** [[https://web.archive.org/web/20160402225843/http://homepage.ntlworld.com/edmund.grimley-evans/cc500/][cc500]] +*** [[https://web.archive.org/web/20160402225843/https://homepage.ntlworld.com/edmund.grimley-evans/cc500/][cc500]] ** rain1's Bootstrapping Wiki: https://bootstrapping.miraheze.org/wiki/Main_Page ** rain1's hex86 https://notabug.org/rain1/hex86/src/master/tests/hex0b3.hex86 diff --git a/README b/README index 49dfee0c..cfcfd5a1 100644 --- a/README +++ b/README @@ -7,7 +7,7 @@ System. Since version 0.22 it has again helped to halve the size of opaque, uninspectable binary seeds that are currently being used in the [[https://guix.gnu.org/blog/2020/guix-further-reduces-bootstrap-seed-to-25][Further Reduced Binary Seed bootstrap]] of [[https://www.gnu.org/software/guix][GNU Guix]]. The final goal is to -help create a full-source bootstrap as part of the [[http://bootstrappable.org][bootstrappable builds]] +help create a full-source bootstrap as part of the [[https://bootstrappable.org][bootstrappable builds]] effort for UNIX-like operating systems. The Scheme interpreter is written in ~5,000 LOC of simple C, and the C @@ -25,7 +25,7 @@ Reduced Binary Seed bootstrap for the gnutools triplet: glibc-2.2.5, binutils-2.20.1, gcc-2.95.3. This is enough to bootstrap Guix for i686-linux, x86_64-linux, armhf-linux and aarch64-linux. -Mes is inspired by The Maxwell Equations of Software: [[http://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf][LISP-1.5]] -- John +Mes is inspired by The Maxwell Equations of Software: [[https://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf][LISP-1.5]] -- John McCarthy page 13, GNU Guix's source/binary packaging transparency and Jeremiah Orians's [[https://github.com/oriansj/stage0][stage0]] ~500 byte self-hosting hex assembler. @@ -76,7 +76,7 @@ General Public Licence version 3 or later. See the file [[file:COPYING][COPYING [7] https://www.cs.indiana.edu/chezscheme/syntax-case/old-psyntax.html [8] https://www.nongnu.org/nyacc [9] https://gitlab.com/janneke/tinycc - [10] [[http://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf]] + [10] [[https://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf]] [11] https://savannah.nongnu.org/projects/stage0 [12] https://nlnet.nl/project/GNUMes [13] https://nlnet.nl/project/GNUMes-arm diff --git a/doc/fdl-1.3.texi b/doc/fdl-1.3.texi index cb71f05a..11dc8127 100644 --- a/doc/fdl-1.3.texi +++ b/doc/fdl-1.3.texi @@ -6,7 +6,7 @@ @display Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. -@uref{http://fsf.org/} +@uref{https://fsf.org/} Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -414,7 +414,7 @@ The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See -@uref{http://www.gnu.org/copyleft/}. +@uref{https://www.gnu.org/copyleft/}. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this diff --git a/doc/mes.texi b/doc/mes.texi index 28e1c2bb..bdf2c420 100644 --- a/doc/mes.texi +++ b/doc/mes.texi @@ -204,7 +204,7 @@ Freedom 1. @section Reproducible Builds The current Reproducible Builds effort incubated in the Debian -project@footnote{@url{http://debian.org, The Debian Project}} and was +project@footnote{@url{https://debian.org, The Debian Project}} and was organized by Lunar. Quoting the Reproducible Builds website@footnote{@url{https://reproducible-builds.org/,Reproducible Builds}} @@ -365,7 +365,7 @@ Most computers work pretty well so apparently there is not a pressing need to inspect and study all of these codes. At the same time it is tricky to fully trust@footnote{ Ken Thompson's 1984 Turing award acceptance speech -@url{http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf, +@url{https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf, Reflections on Trusting Tust}.} a computer that was bootstrapped in this way. @@ -461,7 +461,7 @@ and mescc-tools can be removed. As fate would have it, I stumbled upon this @url{https://queue.acm.org/detail.cfm?id=1039523, interview with Alan Kay}, where he shares a revelation he had when reading John McCarthy's -@url{http://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf, +@url{https://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf, LISP-1.5} manual: @quotation @@ -553,11 +553,11 @@ in the Mes source tree for additional details. GNU Mes depends on the following packages: @itemize -@item @url{http://gnu.org/software/guile/, GNU Guile}, version 2.0.13 or +@item @url{https://gnu.org/software/guile/, GNU Guile}, version 2.0.13 or later, including 2.2.x and 3.0.x, -@item @url{http://www.gnu.org/software/make/, GNU Make}. +@item @url{https://www.gnu.org/software/make/, GNU Make}. @item @url{https://savannah.gnu.org/projects/nyacc/, NYACC}, version 1.00.2, -@item @url{http://gcc.gnu.org, GCC's gcc}, version 2.95.3 or later, including 10.2.0, +@item @url{https://gcc.gnu.org, GCC's gcc}, version 2.95.3 or later, including 10.2.0, @item @url{https://savannah.gnu.org/projects/mescc-tools/, mescc-tools}, version 1.4.0, @end itemize @@ -693,7 +693,7 @@ responsibility. The Reduced Binary Seed bootstrap currently adopted by Guix@footnote{See @file{gnu/packages/commencement.scm} in the @var{master} branch in Guix git -@url{http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/commencement.scm}}. +@url{https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/commencement.scm}}. In its intiial form it is only available for x86-linux and armhf-linux. Currently, it goes like this: @@ -1155,8 +1155,8 @@ Porting MesCC: The Perfect Setup to hack on Mes is basically the perfect setup used for Guile hacking (@pxref{Using Guile in Emacs,,, guile, Guile Reference Manual}). First, you need more than an editor, you need -@url{http://www.gnu.org/software/emacs, Emacs}, empowered by the -wonderful @url{http://nongnu.org/geiser/, Geiser}. +@url{https://www.gnu.org/software/emacs, Emacs}, empowered by the +wonderful @url{https://nongnu.org/geiser/, Geiser}. Geiser allows for interactive and incremental development from within Emacs: code compilation and evaluation from within buffers, access to @@ -1181,7 +1181,7 @@ Scheme code in Mes is written in a purely functional style. @cindex coding style When writing Scheme code, we follow common wisdom among Scheme programmers. In general, we follow the -@url{http://mumble.net/~campbell/scheme/style.txt, Riastradh's Lisp +@url{https://mumble.net/~campbell/scheme/style.txt, Riastradh's Lisp Style Rules}. This document happens to describe the conventions mostly used in Guile’s code too. It is very thoughtful and well written, so please do read it.