Skip to content
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 new but ignored warning option -Wdate-time. #511

Closed
wants to merge 1 commit into from

Conversation

Bluehorn
Copy link

Rationale: This would be helpful for the Debian reproducible builds
effort, described at https://wiki.debian.org/ReproducibleBuilds

Basically, the warning is used to detect where the time macros
__TIME__, __DATE__ etc. are used, but this makes SWIG fail because
of the unrecognized option.

Please see my email on swig-devel and this feature request for more background.

Rationale: This would be helpful for the Debian reproducible builds
effort, described at https://wiki.debian.org/ReproducibleBuilds

Basically, the warning is used to detect where the time macros
__TIME__, __DATE__ etc. are used, but this makes SWIG fail because
of the unrecognized option.
@wsfulton
Copy link
Member

wsfulton commented Sep 9, 2015

@ojwb, Agreed, but this is a non-ideal but pragmatic change, see the swig-devel discussion on this at http://thread.gmane.org/gmane.comp.programming.swig.devel/23717. Could you respond to that discussion. Also, as you know Debian quite well, perhaps you can guide the appropriate project to sort it out properly?

@ojwb
Copy link
Member

ojwb commented Sep 9, 2015

I'd be much more sold on a wrong but pragmatic change if there were many affected packages, but only two have been mentioned so far. So to me, the appropriate fix seems to be patching the build systems of the Debian subversion and unbound packages to not do swig $(CPPFLAGS) [...] (or equivalent).

Will follow up in that thread.

@ojwb
Copy link
Member

ojwb commented Sep 14, 2015

Done.

@Bluehorn Bluehorn closed this Sep 21, 2015
@Bluehorn
Copy link
Author

Closing this pull request, I concur with Ollys arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants