-
Notifications
You must be signed in to change notification settings - Fork 2.8k
all.sh: Fix check_headers_in_cpp #2407
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
Conversation
When all.sh invokes check_headers_in_cpp, a backup config.h exists. This causes a stray difference vs cpp_dummy_build.cpp. Fix by only collecting the *.h files in include/mbedtls. Change-Id: Ifd415027e856858579a6699538f06fc49c793570
RonEld
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM, however a ChangeLog entry is needed
23a355c to
995d5c1
Compare
RonEld
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
mpg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks for fixing this.
|
Note: I've taken the liberty of editing the PR description regarding backporting, which happens not to be needed here. |
|
This has two approving reviews and a passing CI, a valid CLA, fixes a legitimate bug with an appropriate ChangeLog entry and is not waiting for backports, so labeling as ready for merge. |
|
This PR didn't apply cleanly on mbedtls-2.16, so I've raised a backport PR at #2412 Please review. Thanks. |
Description
When all.sh invokes check_headers_in_cpp, a backup config.h exists. This
causes a stray difference vs cpp_dummy_build.cpp. Fix by only collecting
the *.h files in include/mbedtls.
Fixes #2406.
Status
READY
Requires Backporting
[edited by mpg]
Migrations
If there is any API change, what's the incentive and logic for it.
NO
Additional comments
Any additional information that could be of interest
Todos
Steps to test or reproduce
./tests/scripts/all.sh build_default_make_gcc_and_cxx