Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] mono broken on aarch64
@ 2023-10-24 22:36 camj2
  0 siblings, 0 replies; only message in thread
From: camj2 @ 2023-10-24 22:36 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

New issue by camj2 on void-packages repository

https://github.com/void-linux/void-packages/issues/46881

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`.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-10-24 22:36 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-24 22:36 [ISSUE] mono broken on aarch64 camj2

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).