ovos-buildroot: Build errors
Build Environment
-
Raspberry pi 4 2 GB
-
Ubuntu 20.04.2 LTS
-
gcc, gcc++
-
subversion
-
qttools5-dev
-
qttools5-dev-tools
-
python
-
git clone latest copy of OpenVoiceOS as per README
warning occurs when running make rpi4_64-gui-config: -
config rpi4_64-gui
make -C buildroot BR2_EXTERNAL=../buildroot-external "rpi4_64-gui_defconfig"
make[1]: Entering directory '/home/ubuntu/OpenVoiceOS/buildroot'
WARNING: unmet direct dependencies detected for BR2_PACKAGE_PYTHON_PROTOBUF
Depends on [n]: (BR2_PACKAGE_PYTHON [=n] || BR2_PACKAGE_PYTHON3 [=y]) && (BR2_HOSTARCH [=aarch64]=x86_64 || BR2_HOSTARCH [=aarch64]=x86)
Selected by [y]:
- BR2_PACKAGE_PYTHON_PYCHROMECAST [=y]
WARNING: unmet direct dependencies detected for BR2_PACKAGE_PYTHON_PROTOBUF
Depends on [n]: (BR2_PACKAGE_PYTHON [=n] || BR2_PACKAGE_PYTHON3 [=y]) && (BR2_HOSTARCH [=aarch64]=x86_64 || BR2_HOSTARCH [=aarch64]=x86)
Selected by [y]:
- BR2_PACKAGE_PYTHON_PYCHROMECAST [=y]
#
# configuration written to /home/ubuntu/OpenVoiceOS/buildroot/.config
#
make[1]: Leaving directory '/home/ubuntu/OpenVoiceOS/buildroot'
Then after running make rpi4_64-gui the following error occurs: -
/home/ubuntu/OpenVoiceOS/buildroot/output/host/bin/ccache /usr/bin/g++ -fno-PIE -c -O2 -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o caller-save.o -MT caller-save.o -MMD -MP -MF ./.deps/caller-save.TPo ../../gcc/caller-save.c
/home/ubuntu/OpenVoiceOS/buildroot/output/host/bin/ccache /usr/bin/g++ -fno-PIE -c -O2 -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -I/home/ubuntu/OpenVoiceOS/buildroot/output/host/include -I../../gcc/../libdecnumber -I../../gcc/../libdecnumber/dpd -I../libdecnumber -I../../gcc/../libbacktrace -o calls.o -MT calls.o -MMD -MP -MF ./.deps/calls.TPo ../../gcc/calls.c
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[4]: *** [Makefile:1117: insn-emit.o] Error 1
make[4]: *** Waiting for unfinished jobs....
rm gcc.pod
make[3]: *** [Makefile:4376: all-gcc] Error 2
make[2]: *** [package/pkg-generic.mk:250: /home/ubuntu/OpenVoiceOS/buildroot/output/build/host-gcc-initial-10.2.0/.stamp_built] Error 2
make[1]: *** [Makefile:84: _all] Error 2
make[1]: Leaving directory '/home/ubuntu/OpenVoiceOS/buildroot'
Not sure what dependency i am missing re: warning? Or if I am doing anything obviously wrong?
Thank you!
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 41 (41 by maintainers)
@limitless-code I think that was directed at @j1nx, and somebody will probably get around to it. However, the question belies a certain unfamiliarity that I love to fix, as most git tutorials are WAY too advanced and explain too much at once. I’ve never tried to write it in a single GitHub comment, so here goes.
(Edit: I explain nothing, quite deliberately. Just do the stuff.)
Fork this repo on GitHub, clone your fork, and PR the changes. If you already cloned it from our GitHub, you don’t have to clone it again. One command will switch to your fork:
git remote set-url origin [your_fork_url]Next, make a new branch so you can switch between your changes and the “main” version.
git checkout -b update-readme (outputs "switched to new branch: update-readme")You are now working on your own branch of this repo, separate from the development and production branches that we build and ship. You named it
update-readmebecause I told you to =P but git doesn’t care what you name it.You can make your changes to the readme now. When you’re finished,
You have now added a commit to your feature branch, which you can submit to us. If you want to verify that it worked, you can type
git log. It will open in your pager. Your new commit should be at the top, with the message “update readme”. That’s how it will look in this repo, too. When you’re finished, typegit push origin update-readmeGitHub may ask for your credentials at this point. Then it will push your changes to GitHub, on your fork, in a branch called
update-readme.GitHub should send back a link, which will be near the bottom of the terminal output. That link will open a pull request back here. Open the link and hit “submit.”
Congratulations. You have just used git to submit changes to open source software. You don’t need to know why you did any of that. Half of it is self explanatory. The rest will come with time. Nuking and starting over is usually the wrong answer. Tuts just suck, so nobody ever gets that far, and most end up thinking of git as “that thing that makes me nuke my code once in a while.”
On it.
Sure, I will hold fire on conclusion 'til I receive new SSD so i can boot to it, test on x86_64 architecture and ensure nothing else is missed.
That won’t happen 'till the after weekend.
Right! Buildroot is a cross compiling system. You do not run it on a rpi but on a normal x86_64 system.
Ah! I forgot about the shout-out, didn’t think about search engines. Makes sense.
For what it’s worth, currently in numbered pre/alpha are OVOS Skill Manager and several of the skills in our Skills Store (available via OSM). OSM is standalone, and should work on any Mycroft build or device (testers sought!) and does not conflict with its first-party counterpart.
It offers the same functionality as MSM, the skill manager that comes with Mycroft, but it also provides access to several repositories that aren’t supported by MycroftAI, Inc. (nor, apart from the OVOS Skill Store, by us.)
This includes the repos for other Mycroft-based projects, Pling, and a use-at-your-even-more-than-usual-peril interface for Andlo’s Skill List, which the eponymous community member produced by crawling GitHub for everything that looks like a Mycroft skill.