-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
error: memcpy(): too few arguments provided to function-like macro invocation #8994
Comments
Same issue on PowerPC, both with gcc-4.2 and gcc13: https://trac.macports.org/ticket/69624 |
As I already said, "fails to build on macOS 10.12 and earlier". All PowerPC Macs are obviously included in that. |
Fair enough, it was just not yet clear at that moment (for me at least) that the cause of the error are system headers, and we do have instances where something gonna build fine on PowerPC while failing on corresponding Intel systems, due to different compilers and C++ runtime. |
…ke macro Fixes Mbed-TLS#8994 Signed-off-by: Tom Cosgrove <[email protected]>
…ke macro Fixes Mbed-TLS#8994 Signed-off-by: Tom Cosgrove <[email protected]>
…ke macro Fixes Mbed-TLS#8994 Signed-off-by: Tom Cosgrove <[email protected]>
…ke macro Fixes Mbed-TLS#8994 Signed-off-by: Tom Cosgrove <[email protected]>
It builds now for me, thank you for fixing it! |
Summary
mbedtls 3.6.0 fails to build on macOS 10.12 and earlier due to wrong number of arguments to
memcpy
, becausememcpy()
is a function-like macro there.System information
Mbed TLS version (number or commit id): 3.6.0
Operating system and version: macOS 10.12
Configuration (if not default, please attach
mbedtls_config.h
):Compiler and options (if you used a pre-built binary, please indicate how you obtained it): from Xcode 9.2
Additional environment information:
Expected behavior
successful build
Actual behavior
https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/266113/steps/install-port/logs/stdio
Steps to reproduce
Build mbedtls 3.6.0 on macOS 10.12 or earlier
Additional information
Here is how a similar bug was fixed in another project:
https://redmine.lighttpd.net/issues/2772
The text was updated successfully, but these errors were encountered: