Closed orbea closed 4 years ago
It clear that libexpat propably other are not correctly linking (probably link with host ar instead target ar)
Do you have any suggestions on what can be done? Unfortunately without the hardware I can't do much more than blindly test...
I can try a.crossbuild later and test it to my pi3 . I wll tell more after
Thanks! It would be very much appreciated if I could get help making sure the recipe is right after my changes to the buildbot script.
first look https://github.com/libretro/libretro-super/blob/6c22939158d525475e36d2c64f30ae9f21b42c47/recipes/linux/cores-linux-armhf-generic.conf should add AR AR arm-linux-gnueabihf-ar https://github.com/libretro/mame2014-libretro/blob/master/Makefile#L142 AR ?= $(AR)
else
REALCC ?= gcc bad! maybe change REALCC ?= $(GCC)
and see how it goes after this two changes
Thanks for the advice, I think I'm going to try fixing travis first so that it can test any changes. For that I need this to be merged. https://github.com/libretro/libretro-super/pull/662
The buildbot is failing for linux armhf for
mame2014
,mess2014
andume2014
. Bothmame2014
andmess2014
were last updated over a year ago andume2014
is currently missing from the buildbot.They all fail during linking with this error.
See http://p.0bl.net/120209
I can not test this locally, can someone fix this for the buildbot or instruct me what build options this platform needs for successful compilation?
Also see these two PRs. https://github.com/libretro/libretro-super/pull/652 https://github.com/libretro/libretro-super/pull/654