-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Do not hide the build commands by default #6
Comments
For Inadyn I've had |
…d system Initial conversion from lightweight configure with homegrown Makefile.in to using full configure + Makefile.am -- heads up, files may be missing from `make dist` or `make install`! This commit should also fix the last issues with install/unzip mentioned in issue #5 -- resulting README and ChangeLog are now copied to archive. Signed-off-by: Joachim Nilsson <[email protected]>
So ... I've converted to use automake. Default is silent rules disabled, I've tested both Feel free to reopen the issue if you feel this commit isn't sufficient. |
Thanks a lot, I was not referring to a particular security standard or praxis. I just know it from my own experience how annoying it can be to not see the used compiler flags in archived build logs. Your switch to automake solved my issue just perfectly. Thanks for doing it that incredibly fast - I couldn't have done it that fast... Best regards, |
OK, thanks for clarifying. Was just curious if there was anything I could read up on. Glad to help. Will try to get a 2.0 release out this week 👍 |
For security reviews long time after build it is sometimes essential to be able to tell from the build logs
what compiler flags were really used to build the binary. To support such reviews, the build commands
should not be hidden by default.
I intend to work on this issue in the next week, but not today.
The text was updated successfully, but these errors were encountered: