summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2019-02-07 09:24:36 +0100
committerLudovic Courtès <ludo@gnu.org>2019-02-10 22:42:12 +0100
commit23919691f1788ac0e34eba51dfac30358693fae3 (patch)
tree398cabe9fe88d01340824f8dde63696186aeb0ad
parentwebsite: guixdays-arm-hacking: Add backticks. (diff)
downloadguix-artwork-23919691f1788ac0e34eba51dfac30358693fae3.tar.gz
website: guixdays-arm-hacking: Use ellipses.
* website/posts/guixdays-arm-hacking.md: Use HORIZONTAL ELLIPSIS rather than three or two dots.
-rw-r--r--website/posts/guixdays-arm-hacking.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/website/posts/guixdays-arm-hacking.md b/website/posts/guixdays-arm-hacking.md
index 039ad65..0282379 100644
--- a/website/posts/guixdays-arm-hacking.md
+++ b/website/posts/guixdays-arm-hacking.md
@@ -142,7 +142,7 @@ $(guix build --source binutils)` and started looking. There were many obvious
`(("gcc:lib" ,gcc "lib")))))
```
-One more build cycle later and we did it! `/gnu/store/...-binutils-gold-2.31.1`
+One more build cycle later and we did it! `/gnu/store/…-binutils-gold-2.31.1`
existed! We now did two things, we copied our patch over to an aarch64 build
machine and we started cleaning up our package definition on our x86_64 build
machine, where we knew we had a working package definition.
@@ -221,16 +221,16 @@ was added and our build started.
,@(package-native-inputs go-1.4)))
```
-First build, success! `/gnu/store/...-go-1.11.5` exists! OK, but does it
+First build, success! `/gnu/store/…-go-1.11.5` exists! OK, but does it
actually work? `guix build syncthing --system=armhf-linux`.
-`/gnu/store/...-syncthing-1.0.0` exists too! A quick check of `guix refresh
+`/gnu/store/…-syncthing-1.0.0` exists too! A quick check of `guix refresh
--list-dependent go@1.4` showed that we had unlocked 176 new packages for armhf.
Even better, since they had all failed by default due to go@1.11 failing to
build, for each package that did build meant one fewer package which failed to
build which should take a big bite out of our build failures.
-Our next test was syncthing for aarch64. `/gnu/store/...-go-1.11.5` exists!
-`/gnu/store/..-syncthing-1.0.0` ... does not. "`unknown architecture 'armv7-a'`."
+Our next test was syncthing for aarch64. `/gnu/store/…-go-1.11.5` exists!
+`/gnu/store/…-syncthing-1.0.0` ... does not. "`unknown architecture 'armv7-a'`."
It seems that Go is confused which architecture it is building for.
Unfortunately we were reaching the end of our time for hacking, so that will
have to wait for another day. All that was left now was the test failures on