Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1730831 - Mono 5.18.1.28 does not build for aarch64
Summary: Mono 5.18.1.28 does not build for aarch64
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: rawhide
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2019-07-17 19:07 UTC by Timotheus Pokorra
Modified: 2019-07-22 05:07 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-22 05:07:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Timotheus Pokorra 2019-07-17 19:07:45 UTC 
see build https://koji.fedoraproject.org/koji/taskinfo?taskID=36304162

These are the relevant lines in the build log:

BUILDSTDERR: In file included from ../../mono/utils/mono-machine.h:21,
BUILDSTDERR:                  from ../../mono/utils/mono-context.h:16,
BUILDSTDERR:                  from mono-context.c:459:
BUILDSTDERR: mono-context.c: In function 'mono_sigctx_to_monoctx':
BUILDSTDERR: mono-context.c:474:17: error: dereferencing pointer to incomplete type 'struct fpsimd_context'
BUILDSTDERR:   474 |  g_assert (fpctx->head.magic == FPSIMD_MAGIC);
BUILDSTDERR:       |                 ^~
Comment 1 Timotheus Pokorra 2019-07-20 21:09:03 UTC 
Seems it builds now in Rawhide without changes, according to Koschei.
I will close the bug on Monday, if the build succeeds.
Comment 2 Timotheus Pokorra 2019-07-22 05:07:25 UTC 
It seems something outside of Mono was broken in Rawhide, it is working again.
Note You need to log in before you can comment on or make changes to this bug.