-
-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
Build failed #15
Comments
Are the GTK development libraries installed? |
For clarification, this is an issue with upstream GTK, it appears gobject-introspection is missing on the host device, as far as I can tell. |
Ok! I'll figure out how to add that and try again and revert! Thanks for the quick response. |
It should be a relatively quick |
Thanks - maybe good to add that to the pre-requisites list. |
Got a bit further.. Why would it be looking for a .exe file? |
If you use |
but is that something I can control or do I need to change your build files? |
just install dart and rerun it |
The dap package can be disabled in menu config, |
Thanks for the quick responses! Installed dart. This is wonderfully mesmerizing watching it all stream by in the terminal. Have you all considered switching to the rust version of coreutils instead of the c ones? |
I'd certainly like to make the switch at some point, not sure how complete the rust coreutils are at this point, though. |
Oops - one more pre-requesite needed. /bin/bash: flutter: command not found Try try again! |
Ok - that sort of worked, then this happened: [ +4 ms] "flutter linux" took 2,668ms. |
From here, when the pangolin step errors out, you'll need to |
Yes, I did that - it led to some progress, but what do I do about the missing yaml file? |
The missing yaml file should not be causing a problem, you can try |
Ok, had to issue another pre-requisite command: |
Yeah, this process is significantly resource intensive, but it looks like your build completed successfully and has moved on to image packaging. The CPIO image is only required for the legacy image - if you just want an EFI image, you can turn off CPIO and ISO9660 in filesystem options, I'm not sure how the BTRFS image tool works in low-memory environments. Thanks for making this issue, it will be a very helpful reference in making our builds completely reproducible :) |
Try source ~/.profile |
On the build machine, check that an init system is selected under target options |
I could not find that option in the config manager - Target options were just machine types like x64... |
Describe the bug
I followed the instructions to try a build today with the current master
What kind of a bug is it?
Make halted
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Expected a build
Screenshots
Halted with these error..
CC libgdk_3_la-gdkmarshalers.lo
make[6]: *** No rule to make target 'Gdk-3.0.typelib', needed by 'all-am'. Stop.
make[6]: *** Waiting for unfinished jobs....
CC libgdk_3_la-gdkresources.lo
make[5]: *** [Makefile:1663: all-recursive] Error 1
make[4]: *** [Makefile:1092: all] Error 2
make[3]: *** [Makefile:746: all-recursive] Error 1
make[2]: *** [Makefile:619: all] Error 2
make[1]: *** [package/pkg-generic.mk:270: /home/john/buildroot/output/build/libgtk3-3.24.30/.stamp_built] Error 2
make: *** [Makefile:84: _all] Error 2
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: