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

Remaining compiler warnings in 479fe9c #138

Closed
Wikinaut opened this issue Nov 5, 2015 · 3 comments
Closed

Remaining compiler warnings in 479fe9c #138

Wikinaut opened this issue Nov 5, 2015 · 3 comments

Comments

@Wikinaut
Copy link
Contributor

Wikinaut commented Nov 5, 2015

479fe9c still results in these warnings (only warnings are shown): http://dpaste.com/3DWZ4VP

Created with

(git pull)
./autogen.sh
./configure --enable-debug
make &>make.log
agrep -d "^/bin/sh" warning make.log > make-warnings.txt
(uploaded to http://dpaste.com/3DWZ4VP )

ProTip: I used agrep: https://github.com/Wikinaut/agrep because the option "-d" allows to define a "record" which is then printed, if if a match within is found (here: "warning").

@Wikinaut Wikinaut changed the title Compiler warnings in Compiler warnings in 479fe9c37055ecf8004f4eeb9bcb8dcc7c1e89c5 Nov 5, 2015
@Wikinaut Wikinaut changed the title Compiler warnings in 479fe9c37055ecf8004f4eeb9bcb8dcc7c1e89c5 Compiler warnings in 479fe9c Nov 5, 2015
@Wikinaut Wikinaut changed the title Compiler warnings in 479fe9c Remaining compiler warnings in 479fe9c Nov 5, 2015
@Wikinaut
Copy link
Contributor Author

Wikinaut commented Nov 5, 2015

@stweil Stefan, hi. I identified some more remaining warnings. See #138 (comment)

@stweil
Copy link
Member

stweil commented Nov 5, 2015

@Wikinaut Most of those warnings also occur in my builds and are less interesting (like -Wsign-compare which can be ignored IMHO), but there are also some warnings which need further investigations (-Warray-bounds).

@Wikinaut
Copy link
Contributor Author

Wikinaut commented Nov 5, 2015

@stweil I informed you, and listed the remaining warnings, because it looked as if you were "hunting" these last (moretheless cosmetic) problems. I really would like to see them disappearing one after the other... :-))

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

No branches or pull requests

3 participants