Skip to content

Commit 0a7d5f9

Browse files
authored
Rollup merge of #150438 - m68k-elf-platform-doc-update, r=Noratrieb
Remove mentions of debootstrap and chroots from the m68k-unknown-none-elf platform support doc I left the mentions of qemu-user-static as it's one of the only easily accessible emulators for m68k, even though you would have to write your own `_start` and such. The C toolchain that is mentioned is also the easiest way I've found so far to get a linker, which is still needed unless I'm missing something. closes #150414 r? @Noratrieb
2 parents e1c13ff + ab1caae commit 0a7d5f9

File tree

1 file changed

+3
-36
lines changed

1 file changed

+3
-36
lines changed

‎src/doc/rustc/src/platform-support/m68k-unknown-none-elf.md‎

Lines changed: 3 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ Bare metal Motorola 680x0
1212

1313
This target requires an m68k build environment for cross-compilation which
1414
is available on Debian, Debian-based systems, openSUSE, and other distributions.
15+
The gnu linker is currently required, as `lld` has no support for the `m68k` architecture
1516

1617
On Debian-based systems, it should be sufficient to install a g++ cross-compiler for the m68k
1718
architecture which will automatically pull in additional dependencies such as
@@ -29,43 +30,9 @@ binaries:
2930
# apt install qemu-user-static
3031
```
3132

32-
To run more complex programs, it will be necessary to set up a Debian/m68k chroot with
33-
the help of the command `debootstrap`:
34-
35-
```text
36-
# apt install debootstrap debian-ports-archive-keyring
37-
# debootstrap --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg --arch=m68k unstable debian-68k http://ftp.ports.debian.org/debian-ports
38-
```
39-
40-
This chroot can then seamlessly entered using the normal `chroot` command thanks to
41-
QEMU user emulation:
42-
43-
```text
44-
# chroot /path/to/debian-68k
45-
```
46-
47-
To get started with native builds, which are currently untested, a native Debian/m68k
48-
system can be installed either on real hardware such as 68k-based Commodore Amiga or
49-
Atari systems or emulated environments such as QEMU version 4.2 or newer or ARAnyM.
50-
51-
ISO images for installation are provided by the Debian Ports team and can be obtained
52-
from the Debian CD image server available at:
53-
54-
[https://cdimage.debian.org/cdimage/ports/current](https://cdimage.debian.org/cdimage/ports/current/)
55-
56-
Documentation for Debian/m68k is available on the Debian Wiki at:
57-
58-
[https://wiki.debian.org/M68k](https://wiki.debian.org/M68k)
59-
60-
Support is available either through the `debian-68k` mailing list:
61-
62-
[https://lists.debian.org/debian-68k/](https://lists.debian.org/debian-68k/)
63-
64-
or the `#debian-68k` IRC channel on OFTC network.
65-
6633
## Building
6734

68-
At least llvm version `19.1.5` is required to build `core` and `alloc` for this target, and currently the gnu linker is required, as `lld` has no support for the `m68k` architecture
35+
At least llvm version `19.1.5` is required to build `core` and `alloc` for this target.
6936

7037
## Cross-compilation
7138

@@ -105,4 +72,4 @@ Very simple programs can be run using the `qemu-m68k-static` program:
10572
qemu-m68k-static your-code
10673
```
10774

108-
For more complex applications, a chroot or native m68k system is required for testing.
75+
For more complex applications, a native (or emulated) m68k system is required for testing.

0 commit comments

Comments
 (0)