-
Notifications
You must be signed in to change notification settings - Fork 17
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
add build note to assembler sources #24
base: master
Are you sure you want to change the base?
Conversation
Does this introduce a dependency on a particular as / binutils version ? |
Good question, I've asked our (RH/Fedora) toolchain people. |
And their answer is "GNU binutils 2.31 is needed or distro binutils where it has been backported (eg. F-29)". So I'll add a check into configure for this feature. |
|
result without the patch
both builds were with distro CFLAGS/LDFLAGS |
The new version with configure-time check for the flag introduces dependency on autoconf-archive. |
Even with the check I still question portability e.g., on F-28 it says:
Why dont you put it with distro flags where you know its available? How do you solve this problem with other packages that come with asm code and dont use autotools e.g. openssl-libcrypto ? |
When distros use the annobin compiler plugin [1], they have complete overview what compiler flags were used for compilation and they are able to perform security checks on the produced binaries. Compiling assembler source can't provide this kind of information by default, so we need the explicit -Wa,--generate-missing-build-notes=yes option during build. When the option is missing, then the annocheck tool reports "GAPS" in the resulting binary. binutils >= 2.31 or older with backport is needed [1] https://fedoraproject.org/wiki/Changes/Annobin Signed-off-by: Dan Horák <[email protected]>
When distros use the annobin compiler plugin [1], they have complete overview
what compiler flags were used for compilation and they are able to perform
security checks on the produced binaries. Compiling assembler source can't
provide this kind of information by default, so we need the explicit
-Wa,--generate-missing-build-notes=yes option during build. When the option is
missing, then the annocheck tool reports "GAPS" in the resulting binary.
[1] https://fedoraproject.org/wiki/Changes/Annobin
Signed-off-by: Dan Horák [email protected]