https://bugs.winehq.org/show_bug.cgi?id=49191
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|armv7l build broken: |armv7l build broken: |dlls/ntdll expression too |dlls/ntdll expression too |complex |complex (compiler default | |'-march=armv6' doesn't | |support | |__sync_add_and_fetch for | |64-bit integers) Hardware|x86 |arm
--- Comment #4 from Anastasius Focht focht@gmx.net --- Hello Austin,
--- quote --- I take it the solution is to build a custom gcc/clang with a different default arch? --- quote ---
I don't think rebuilding the entire toolchain with different default march 'armv6k' or 'armv7' is required/justified here. An alternative is to pass/export '-march=armv6k' or 'armv7' in CFLAGS when running configure since your target CPU does support this instruction set.
https://www.raspberrypi.org/forums/viewtopic.php?t=4256&start=250
--- quote --- And to have a configure check to enforce that? --- quote ---
Yes, it probably makes sense to have a configure check in place. If the compiler doesn't support __sync_add_and_fetch for 64-bit integers it should just bail. Providing an own, slow implementation like other projects do isn't worth the hassle.
https://github.com/mesa3d/mesa/commit/a6a38a03
Regards