void-linux / void-linux/void-packages

mono broken on aarch64

Open
#46,881 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Is this a new report?

Yes

System Info

Void 6.1.54_1 aarch64-musl Unknown notuptodate hold FFF

Package(s) Affected

mono-6.12.0.182_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

When installing mono on an aarch64 platform, in this case a Raspberry Pi 4, all of the mono related files should be installed to /usr/lib/mono.

Running find /usr/lib/mono -type f | wc -l should print 2953, or some other number greater than 1.

Actual behaviour

Running find /usr/lib/mono -type f | wc -l prints 1.

Steps to reproduce
  1. Install mono on an aarch64 architecture
  2. Try running a program using mono, it will most likely error out
  3. I discovered this issue when I was trying to get a Terraria server running

The issue is most likely something related to cross-compiling. If I build mono on my rpi4 using xbps-src, all of the mono related files exist within the /usr/lib/mono directory.

Though if I build mono for aarch64 on my x86_64 desktop, there are no files within /usr/lib/mono.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the mono-6.12.0.182_1 package and the xbps-src cross-build path, comparing its aarch64 build on x86_64 with a native Raspberry Pi build. Inspect the resulting package contents and /usr/lib/mono installation layout. Done means the cross-built aarch64 package installs the expected Mono files and can run a Mono program.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.