Skip to content

Remove mentions of debootstrap and chroots from the m68k-unknown-none-elf platform support doc #150438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rust-bors merged 2 commits into from
Jan 12, 2026
Merged

Remove mentions of debootstrap and chroots from the m68k-unknown-none-elf platform support doc #150438

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7672916
Remove mentions of debootstrap and chroots from the m68k-unknown-none…
knickish Dec 27, 2025
ab1caae
move sentence about gnu ld from 'Building' to 'Requirements' section
knickish Dec 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 3 additions & 36 deletions src/doc/rustc/src/platform-support/m68k-unknown-none-elf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ Bare metal Motorola 680x0

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

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

To run more complex programs, it will be necessary to set up a Debian/m68k chroot with
the help of the command `debootstrap`:

```text
# apt install debootstrap debian-ports-archive-keyring
# debootstrap --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg --arch=m68k unstable debian-68k http://ftp.ports.debian.org/debian-ports
```

This chroot can then seamlessly entered using the normal `chroot` command thanks to
QEMU user emulation:

```text
# chroot /path/to/debian-68k
```

To get started with native builds, which are currently untested, a native Debian/m68k
system can be installed either on real hardware such as 68k-based Commodore Amiga or
Atari systems or emulated environments such as QEMU version 4.2 or newer or ARAnyM.

ISO images for installation are provided by the Debian Ports team and can be obtained
from the Debian CD image server available at:

[https://cdimage.debian.org/cdimage/ports/current](https://cdimage.debian.org/cdimage/ports/current/)

Documentation for Debian/m68k is available on the Debian Wiki at:

[https://wiki.debian.org/M68k](https://wiki.debian.org/M68k)

Support is available either through the `debian-68k` mailing list:

[https://lists.debian.org/debian-68k/](https://lists.debian.org/debian-68k/)

or the `#debian-68k` IRC channel on OFTC network.

## Building

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
At least llvm version `19.1.5` is required to build `core` and `alloc` for this target.

## Cross-compilation

Expand Down Expand Up @@ -105,4 +72,4 @@ Very simple programs can be run using the `qemu-m68k-static` program:
qemu-m68k-static your-code
```

For more complex applications, a chroot or native m68k system is required for testing.
For more complex applications, a native (or emulated) m68k system is required for testing.
Loading