randyrossi
commented
3 years ago If config.h was not created, it means the configure step for VICE did not work. You'll have to look earlier in the log to see what went wrong.
On Sat, Dec 5, 2020 at 9:55 PM Jamin Collins notifications@github.com wrote:
I have tried building on both Arch Linux and Ubuntu 20.04. On both systems I have also tried both of the following toolchains:
- gcc-arm-none-eabi-9-2019-q4-major-x86_64-linux.tar.bz2
- gcc-arm-none-eabi-9-2020-q2-update-x86_64-linux.tar.bz2
In all cases, the builds fail with the following error:
...
Link errors above are expected
rm -f .o .a .elf .lst .img .hex .cir .map ~ CPP main.o CPP kernel.o CPP vicesound.o CPP vicesoundbasedevice.o vicesoundbasedevice.cpp: In member function 'void ViceSoundBaseDevice::Callback(VCHI_CALLBACK_REASON_T, void)': vicesoundbasedevice.cpp:413:32: warning: comparison of integer expressions of different signedness: 'uint32_t' {aka 'long unsigned int'} and 'int32_t' {aka 'long int'} [-Wsign-compare] 413 | if (Msg.u.complete.cookie1 != VC_AUDIO_WRITE_COOKIE1 || vicesoundbasedevice.cpp:414:32: warning: comparison of integer expressions of different signedness: 'uint32_t' {aka 'long unsigned int'} and 'int32_t' {aka 'long int'} [-Wsign-compare] 414 | Msg.u.complete.cookie2 != VC_AUDIO_WRITE_COOKIE2) { CPP viceoptions.o CPP viceapp.o CPP fbl.o CC crt_pi_idx.o CC crt_pi_rgb.o CPP viceemulatorcore.o In file included from third_party/vice-3.3/src/types.h:30, from third_party/vice-3.3/src/sid/sid.h:34, from viceemulatorcore.cpp:31: third_party/vice-3.3/src/vice.h:43:12: fatal error: config.h: No such file or directory 43 | # include
/ Automagically created by the `configure' script. / | ^ ~~~~~ compilation terminated. make: *** [third_party/circle-stdlib/libs/circle/Rules.mk:133: viceemulatorcore.o] Error 1The bmc64 repository and toolchain are under /opt.
I'm using the following build logic:
!/bin/bash
set -euo pipefail
export ARM_HOME=$(find /opt -maxdepth 1 -type d | grep gcc) export PATH=$PATH:$ARM_HOME/bin export ARM_VERSION=$(ls ${ARM_HOME}/lib/gcc/arm-none-eabi/)
env | grep ARM read
./clean_all.sh || true
./make_all.sh ${@} ./make_machines.sh ${@}
An example of the settings made by the above:
ARM_VERSION=9.2.1 ARM_HOME=/opt/gcc-arm-none-eabi-9-2019-q4-major
Submodule status:
git submodule status --recursive
49fddf66e49f48c6368c477ed54e31c463100fff third_party/circle-stdlib (v8.0-24-g49fddf6) fe24b6bebd1532f2a0ee981af12eaf50cc9e97fb third_party/circle-stdlib/libs/circle (Step40) 28aaa63ac6954d1e61706540590303f29e74f96c third_party/circle-stdlib/libs/circle/addon/littlevgl/lv_examples (v6.0) 135c119b204df48daf36bd1d014e1a8348286aa5 third_party/circle-stdlib/libs/circle/addon/littlevgl/lvgl (v6.0) c01f95bcb08278d9e00f9795c7641284d4f89931 third_party/circle-stdlib/libs/circle-newlib (cygwin-3_0_4-release-313-gc01f95bcb) d81c11b8ab61fd5b2da8133aa73c5fe33a0633eb third_party/circle-stdlib/libs/mbedtls (mbedtls-2.16.2)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/randyrossi/bmc64/issues/147, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI3HKBNVBSZOTGMTWYJBDTSTLXCDANCNFSM4UO7ZKGQ .
-- Randy Rossi
- "There are only two things that are hard about computer science; Naming things, Cache Invalidation, and Off-by-one errors."
jamincollins
maitrezoid
rhester72
fearthecowboy
I have tried building on both Arch Linux and Ubuntu 20.04. On both systems I have also tried both of the following toolchains:
In all cases, the builds fail with the following error:
The bmc64 repository and toolchain are under /opt.
I'm using the following build logic:
An example of the settings made by the above:
Submodule status: