website: updates

Author: ilg-ul

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-02-14-arm-none-eabi-gcc-v8-2-1-1-4-released.md

@@ -54,10 +54,10 @@ bug fixes:
 - GDB was built the Git commit ad0f979c9 from 2019-01-29, to fix the bugs
   affecting C++ LTO projects
   [24145](https://sourceware.org/bugzilla/show_bug.cgi?id=24145)
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   by default, the GCC build script fails to create `liblto_plugin-0.dll`
   for static builds with mingw; code to create the plugin was added
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to gcc to fix the Windows LTO with -g bug

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-04-26-arm-none-eabi-gcc-v8-2-1-1-5-released.md

@@ -49,7 +49,7 @@ Compared to the ARM distribution, the build procedure is more or less the
 same and there should be no functional differences, except the following
 bug fixes:
 
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   due to a problem in the GCC configure script and the specifics of the static
   build, LTO was not effective on Windows, and the initial workaround proved
   not effective either; in the new build environment the configure script is
@@ -59,10 +59,10 @@ bug fixes:
 - GDB was built the Git commit ad0f979c9 from 2019-01-29, to fix the bugs
   affecting C++ LTO projects
   [24145](https://sourceware.org/bugzilla/show_bug.cgi?id=24145)
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   by default, the GCC build script fails to create `liblto_plugin-0.dll`
   for static builds with mingw; builds are now using shared libraries
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to gcc to fix the Windows LTO with -g bug

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-05-13-arm-none-eabi-gcc-v8-2-1-1-6-released.md

@@ -47,17 +47,17 @@ Compared to the ARM distribution, the build procedure is more or less the
 same and there should be no functional differences, except the following
 bug fixes:
 
-- [Issue:[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]
+- [[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]:
   the Windows paths with spaces bug apparently was caused by an old version of
   and with the new version (5.0.4) the
   [89249](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89249)
   `gcc.c` patch is no longer needed;
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   due to a problem in the GCC configure script and the specifics of the static
   build, LTO was not effective on Windows, and the initial workaround proved
   not effective either; in the new build environment the configure script is
   enables LTO and it is functional on windows too;
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to binutils to fix the 32-bit objcopy bug

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-05-24-arm-none-eabi-gcc-v8-2-1-1-7-released.md

@@ -47,17 +47,17 @@ Compared to the ARM distribution, the build procedure is more or less the
 same and there should be no functional differences, except the following
 bug fixes:
 
-- [Issue:[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]
+- [[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]:
   the Windows paths with spaces bug apparently was caused by an old version of
   and with the new version (5.0.4) the
   [89249](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89249)
   `gcc.c` patch is no longer needed;
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   due to a problem in the GCC configure script and the specifics of the static
   build, LTO was not effective on Windows, and the initial workaround proved
   not effective either; in the new build environment the configure script is
   enables LTO and it is functional on windows too;
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to binutils to fix the 32-bit objcopy bug

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-07-26-arm-none-eabi-gcc-v7-3-1-1-2-released.md

@@ -125,8 +125,8 @@ The issue was reported to Arm as bug [1838049](https://bugs.launchpad.net/gcc-ar
   `system/src/newlib/_syscalls.c`. The problem was in the project template
   [#317](https://github.com/gnu-mcu-eclipse/eclipse-plugins/issues/317), and
   was fixed in GNU MCU Eclipse plug-ins v4.4.2 (2018-08-27).
-- [[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-  Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+  due to an omission in the build scripts, the content of the `libgcov`
   library is mostly empty; the problem was fixed starting with v8.3.1-1.2.
 
 ## Documentation

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-07-29-arm-none-eabi-gcc-v8-3-1-1-1-released.md

@@ -126,8 +126,8 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-  Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+  due to an omission in the build scripts, the content of the `libgcov`
   library is mostly empty; the problem was fixed starting with v8.3.1-1.2.
 
 ## Documentation

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-10-11-arm-none-eabi-gcc-v8-3-1-1-2-released.md

@@ -104,8 +104,8 @@ There should be no functional changes.
 
 ### `libgcov`
 
-[[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+due to an omission in the build scripts, the content of the `libgcov`
 library was mostly empty; the script was fixed and now the library has the
 expected content.
 

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-11-02-arm-none-eabi-gcc-v8-3-1-1-3-released.md

@@ -100,18 +100,18 @@ thumb/v8-m.main+dp/hard;@mthumb@march=armv8-m.main+fp.dp@mfloat-abi=hard
 
 ## Bug fixes
 
-- [[#4]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/4)
-Due to a bug in the build scripts, the Windows `gdb-py` had a hard-wired
+- [[#4](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/4)]:
+due to a bug in the build scripts, the Windows `gdb-py` had a hard-wired
 dependency to Python 2.7.13 and failed to start on other versions; fixed;
-- [[#3]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/3)
-Due to a bug in the build scripts, the macOS `gdb-py` had a wrong
+- [[#3](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/3)]:
+due to a bug in the build scripts, the macOS `gdb-py` had a wrong
 dependency and failed to start; fixed;
-- [[#2]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/2)
-Due to a bug in the build scripts, the Windows binaries included two
+- [[#2](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/2)]:
+due to a bug in the build scripts, the Windows binaries included two
 copies of the `docs` folder, one in root and one in the `share` folder;
 the script was fixed and now there is only one copy in `share/docs`.
-- [[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+due to an omission in the build scripts, the content of the `libgcov`
 library was mostly empty; the script was fixed and now the library has the
 expected content.
 
@@ -143,7 +143,7 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#5]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)
+- [[#5](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)]:
 the `arm-none-eabi-gdb-py` fails to start on Ubuntu (and possibly
 other Debian) systems, it fails with a message like:
 ```console

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-12-06-arm-none-eabi-gcc-v8-3-1-1-4-released.md

@@ -123,7 +123,7 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#5]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)
+- [[#5](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)]:
 the `arm-none-eabi-gdb-py` fails to start on Ubuntu (and possibly
 other Debian) systems, it fails with a message like:
 ```console

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2019-12-06-arm-none-eabi-gcc-v9-2-1-1-1-released.md

@@ -127,7 +127,7 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#5]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)
+- [[#5](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)]:
 the `arm-none-eabi-gdb-py` fails to start on Ubuntu (and possibly
 other Debian) systems, it fails with a message like:
 ```console

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2020-07-27-arm-none-eabi-gcc-v9-3-1-1-2-released.md

@@ -116,8 +116,8 @@ thumb/v8-m.main+dp/hard;@mthumb@march=armv8-m.main+fp.dp@mfloat-abi=hard
 
 ## Bug fixes
 
-- [[#7]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/7)
-Due to a bug in the build scripts, the non-nano libraries were also build
+- [[#7](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/7)]:
+due to a bug in the build scripts, the non-nano libraries were also build
 without C++ exceptions support; fixed.
 
 ## Enhancements

website/_xpack.github.io/_posts/releases/arm-none-eabi-gcc/2023-09-21-arm-none-eabi-gcc-v12-3-1-1-2-released.md

@@ -223,7 +223,7 @@ platforms, support for Guile scripting in GDB is currently not available.
 
 ## Bug fixes
 
-- [[#33](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/33)]
+- [[#33](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/33)]:
   due to a an issue in the build scripts, on GNU/Linux,
   the `arm-none-eabi-gdb` was built without ELF support; fixed
 

website/blog/2019-02-14-arm-none-eabi-gcc-v8-2-1-1-4-released.mdx

@@ -60,10 +60,10 @@ bug fixes:
 - GDB was built the Git commit ad0f979c9 from 2019-01-29, to fix the bugs
   affecting C++ LTO projects
   [24145](https://sourceware.org/bugzilla/show_bug.cgi?id=24145)
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   by default, the GCC build script fails to create `liblto_plugin-0.dll`
   for static builds with mingw; code to create the plugin was added
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to gcc to fix the Windows LTO with -g bug

website/blog/2019-04-26-arm-none-eabi-gcc-v8-2-1-1-5-released.mdx

@@ -55,7 +55,7 @@ Compared to the ARM distribution, the build procedure is more or less the
 same and there should be no functional differences, except the following
 bug fixes:
 
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   due to a problem in the GCC configure script and the specifics of the static
   build, LTO was not effective on Windows, and the initial workaround proved
   not effective either; in the new build environment the configure script is
@@ -65,10 +65,10 @@ bug fixes:
 - GDB was built the Git commit ad0f979c9 from 2019-01-29, to fix the bugs
   affecting C++ LTO projects
   [24145](https://sourceware.org/bugzilla/show_bug.cgi?id=24145)
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   by default, the GCC build script fails to create `liblto_plugin-0.dll`
   for static builds with mingw; builds are now using shared libraries
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to gcc to fix the Windows LTO with -g bug

website/blog/2019-05-13-arm-none-eabi-gcc-v8-2-1-1-6-released.mdx

@@ -53,17 +53,17 @@ Compared to the ARM distribution, the build procedure is more or less the
 same and there should be no functional differences, except the following
 bug fixes:
 
-- [Issue:[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]
+- [[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]:
   the Windows paths with spaces bug apparently was caused by an old version of
   and with the new version (5.0.4) the
   [89249](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89249)
   `gcc.c` patch is no longer needed;
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   due to a problem in the GCC configure script and the specifics of the static
   build, LTO was not effective on Windows, and the initial workaround proved
   not effective either; in the new build environment the configure script is
   enables LTO and it is functional on windows too;
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to binutils to fix the 32-bit objcopy bug

website/blog/2019-05-24-arm-none-eabi-gcc-v8-2-1-1-7-released.mdx

@@ -53,17 +53,17 @@ Compared to the ARM distribution, the build procedure is more or less the
 same and there should be no functional differences, except the following
 bug fixes:
 
-- [Issue:[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]
+- [[#4](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/4)]:
   the Windows paths with spaces bug apparently was caused by an old version of
   and with the new version (5.0.4) the
   [89249](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89249)
   `gcc.c` patch is no longer needed;
-- [Issue:[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]
+- [[#3](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/3)]:
   due to a problem in the GCC configure script and the specifics of the static
   build, LTO was not effective on Windows, and the initial workaround proved
   not effective either; in the new build environment the configure script is
   enables LTO and it is functional on windows too;
-- [Issue:[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]
+- [[#1](https://github.com/gnu-mcu-eclipse/arm-none-eabi-gcc-build/issues/1)]:
   the `liblto_plugin` copied/linked to the `lib/bdf-plugins` for `ar`
   to find it and be able to process archives with LTO objects
 - a patch was applied to binutils to fix the 32-bit objcopy bug

website/blog/2019-07-26-arm-none-eabi-gcc-v7-3-1-1-2-released.mdx

@@ -119,8 +119,8 @@ The issue was reported to Arm as bug [1838049](https://bugs.launchpad.net/gcc-ar
   `system/src/newlib/_syscalls.c`. The problem was in the project template
   [#317](https://github.com/gnu-mcu-eclipse/eclipse-plugins/issues/317), and
   was fixed in GNU MCU Eclipse plug-ins v4.4.2 (2018-08-27).
-- [[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-  Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+  due to an omission in the build scripts, the content of the `libgcov`
   library is mostly empty; the problem was fixed starting with v8.3.1-1.2.
 
 ## Documentation

website/blog/2019-07-29-arm-none-eabi-gcc-v8-3-1-1-1-released.mdx

@@ -120,8 +120,8 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-  Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+  due to an omission in the build scripts, the content of the `libgcov`
   library is mostly empty; the problem was fixed starting with v8.3.1-1.2.
 
 ## Documentation

website/blog/2019-10-11-arm-none-eabi-gcc-v8-3-1-1-2-released.mdx

@@ -98,8 +98,8 @@ There should be no functional changes.
 
 ### `libgcov`
 
-[[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+due to an omission in the build scripts, the content of the `libgcov`
 library was mostly empty; the script was fixed and now the library has the
 expected content.
 

website/blog/2019-11-02-arm-none-eabi-gcc-v8-3-1-1-3-released.mdx

@@ -94,18 +94,18 @@ thumb/v8-m.main+dp/hard;@mthumb@march=armv8-m.main+fp.dp@mfloat-abi=hard
 
 ## Bug fixes
 
-- [[#4]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/4)
-Due to a bug in the build scripts, the Windows `gdb-py` had a hard-wired
+- [[#4](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/4)]:
+due to a bug in the build scripts, the Windows `gdb-py` had a hard-wired
 dependency to Python 2.7.13 and failed to start on other versions; fixed;
-- [[#3]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/3)
-Due to a bug in the build scripts, the macOS `gdb-py` had a wrong
+- [[#3](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/3)]:
+due to a bug in the build scripts, the macOS `gdb-py` had a wrong
 dependency and failed to start; fixed;
-- [[#2]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/2)
-Due to a bug in the build scripts, the Windows binaries included two
+- [[#2](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/2)]:
+due to a bug in the build scripts, the Windows binaries included two
 copies of the `docs` folder, one in root and one in the `share` folder;
 the script was fixed and now there is only one copy in `share/docs`.
-- [[#1]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)
-Due to an omission in the build scripts, the content of the `libgcov`
+- [[#1](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/1)]:
+due to an omission in the build scripts, the content of the `libgcov`
 library was mostly empty; the script was fixed and now the library has the
 expected content.
 
@@ -137,7 +137,7 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#5]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)
+- [[#5](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)]:
 the `arm-none-eabi-gdb-py` fails to start on Ubuntu (and possibly
 other Debian) systems, it fails with a message like:
 ```console

website/blog/2019-12-06-arm-none-eabi-gcc-v8-3-1-1-4-released.mdx

@@ -117,7 +117,7 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#5]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)
+- [[#5](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)]:
 the `arm-none-eabi-gdb-py` fails to start on Ubuntu (and possibly
 other Debian) systems, it fails with a message like:
 ```console

website/blog/2019-12-06-arm-none-eabi-gcc-v9-2-1-1-1-released.mdx

@@ -125,7 +125,7 @@ and macOS; not yet available on Windows
 
 ## Known problems
 
-- [[#5]](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)
+- [[#5](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/issues/5)]:
 the `arm-none-eabi-gdb-py` fails to start on Ubuntu (and possibly
 other Debian) systems, it fails with a message like:
 ```console