releases: mention new or1k-toolhchain-build location

Author: stffrdhrn

index.md

@@ -62,14 +62,10 @@ some basic examples is also available
 You can install pre-compiled toolchains and install them on your
 Linux system. We have prebuilt-toolchains for releases of the
 different components that are preferably installed
-to `/opt/toolchains/or1k-elf`. You can find releases in the following locations:
+to `/opt/toolchains/or1k-elf`. You can find releases at:
 
- * [openrisc/newlib/releases](https://github.com/openrisc/newlib/releases) Older
-   releases from the OpenRISC community last published in May 2016. Used the
-   old non-upstreamed gcc port.
- * [Embecosm OpenRISC toolchain top-of-tree](https://embecosm.com/downloads/tool-chain-downloads/#openrisc-top-of-tree-compilers) Embecosm
-   produced toolchain builds up until 2023.  Unforthunately this effort stopped.
- * [openrisc/or1k-gcc/releases](https://github.com/openrisc/or1k-gcc/releases) The latest releases from OpenRISC.
+ * [or1k-toolchain-build/Releases](https://github.com/stffrdhrn/or1k-toolchain-build/releases) Latest
+   OpenRISC toolchain releases.
 
 After downloading a release you can extract it anywhere in your
 filesystem, we recommend to `/opt/toolchains/or1k-elf/`. You need to add
@@ -78,13 +74,12 @@ the toolchain to your path:
 ```
 export PATH=/opt/toolchains/or1k-elf/bin:${PATH}
 ```
+#### Historical releases.
 
-### Development Build status
-
-Whenever something is pushed to the newlib repository, the current
-development versions of Binutils, GCC, (or1k) Newlib and GDB are
-automatically build
-at <a href="https://travis-ci.org/openrisc/newlib">Travis CI</a>.
+ * [openrisc/newlib/releases](https://github.com/openrisc/newlib/releases) Older
+   releases from the OpenRISC community last published in May 2016. Used the
+   old non-upstreamed gcc port.
+ * [Embecosm OpenRISC toolchain top-of-tree](https://embecosm.com/downloads/tool-chain-downloads/#openrisc-top-of-tree-compilers) Embecosm
+   produced toolchain builds up until 2023.  Unforthunately this effort stopped.
+ * [openrisc/or1k-gcc/releases](https://github.com/openrisc/or1k-gcc/releases) Older development releases from OpenRISC.
 
-Current build
-status: <a href="https://travis-ci.org/openrisc/newlib"><img src="https://travis-ci.org/openrisc/newlib.svg?branch=or1k"></a>

multicore.md

@@ -14,7 +14,7 @@ to build newlib with the environment
 variable `CFLAGS="-D__OR1K_MULTICORE__"`:
 
 ```
-../newlib/configure --target=or1k-elf \
+../newlib/configure --target=or1k-nonemc-elf \
 	--prefix=$PREFIX \
 	CFLAGS_FOR_TARGET="-D__OR1K_MULTICORE__"
 ```
@@ -25,19 +25,18 @@ variable `CFLAGS="-D__OR1K_MULTICORE__"`:
 You can install pre-compiled toolchains and install them on your
 Linux system. We have prebuilt-toolchains for releases of the
 different components that are preferably installed
-to `/opt/toolchains/or1k-elf-multicore` or `/opt/toolchains/or1k-elf`.
+to `/opt/toolchains/or1k-nonemc-elf`.
 You can find some older multicore releases
-<a href="https://github.com/openrisc/newlib/releases">here</a>. The last ones being:</p>
+<a href="https://github.com/stffrdhrn/or1k-toolchain-build/releases">here</a>. The latest ones being:</p>
 
- * <a href="https://github.com/openrisc/newlib/releases/download/v2.3.0-1/or1k-elf-multicore_gcc4.9.3_binutils2.26_newlib2.3.0-1_gdb7.11.tgz">GCC 4.9.2, Binutils 2.26, Newlib 2.3.0 (+or1k backports), GDB 7.11
- * <a href="https://github.com/openrisc/newlib/releases/download/v2.3.0-1/or1k-elf-multicore_gcc5.2.0_binutils2.26_newlib2.3.0-1_gdb7.11.tgz">GCC 5.2.0, Binutils 2.26, Newlib 2.3.0 (+or1k backports), GDB 7.11
+ * [GCC 14.2.0, newlib 4.5.0, binutils 2.43.1](https://github.com/stffrdhrn/or1k-toolchain-build/releases/download/or1k-14.2.0-20250329/or1k-nonemc-elf-14.2.0-20250329.tar.xz]
 
 After downloading a release you can extract it anywhere in your
-filesystem, preferable to `/opt/toolchains/or1k-elf/`. You need to add
+filesystem, preferable to `/opt/toolchains/or1k-nonemc-elf/`. You need to add
 the toolchain to your path:
 
 ```
-export PATH=/opt/toolchains/or1k-elf/bin:${PATH}
+export PATH=/opt/toolchains/or1k-nonemc-elf/bin:${PATH}
 ```