Bug 253163 - devel/glib20 fails to build on aarch64 at 285/1079 with "ninja: build stopped: subcommand failed."
Summary: devel/glib20 fails to build on aarch64 at 285/1079 with "ninja: build stopped...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Only Me
Assignee: freebsd-desktop (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-01 14:54 UTC by Dan Kotowski
Modified: 2021-02-02 17:01 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (desktop)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Kotowski 2021-02-01 14:54:15 UTC
Building glib20-2.66.4 for 13.0-ALPHA3 on aarch64:

```
[285/1079] /usr/local/bin/meson --internal exe --capture gobject/glib-enumtypes.h -- /usr/ports/devel/glib20/work/.bin/python3 gobject/glib-mkenums --template ../gobject/glib-enumtypes.h.template ../gobject/../glib/gunicode.h
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/glib20
```
Comment 1 Dan Kotowski 2021-02-01 15:02:11 UTC
With `MAKE_JOBS_UNSAFE=yes`, still fails but a bit further on:

```
[293/1079] /usr/ports/devel/glib20/work/glib-2.66.4/_build/glib/gtester -k --quiet --i-know-this-is-deprecated -o glib/tests/tmpsample.xml --test-arg=--gtester-selftest /usr/ports/devel/glib20/work/glib-2.66.4/_build/glib/gtester
FAILED: glib/tests/tmpsample.xml
/usr/ports/devel/glib20/work/glib-2.66.4/_build/glib/gtester -k --quiet --i-know-this-is-deprecated -o glib/tests/tmpsample.xml --test-arg=--gtester-selftest /usr/ports/devel/glib20/work/glib-2.66.4/_build/glib/gtester
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/glib20
```
Comment 2 Dima Panov freebsd_committer freebsd_triage 2021-02-01 16:01:43 UTC
(In reply to Dan Kotowski from comment #1)
It was discussed a month ago in desktop@ mailing list.

This is because the kernel on the host does not support eventfd, while the jail 
does. 


Anyway, running new jain on an old host is unsupported, please upgrade host.
Comment 3 Dan Kotowski 2021-02-02 17:01:00 UTC
This was the solution.