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

warning at compilation #29

Closed
GoogleCodeExporter opened this issue Aug 3, 2015 · 4 comments
Closed

warning at compilation #29

GoogleCodeExporter opened this issue Aug 3, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. unzip 
2. ./configure
3. make

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?

ubuntu 10.04 x64

Please provide any additional information below.

--------------------------

lsyncd.c: In function ‘reset_options’:
lsyncd.c:966: warning: comparison with string literal results in unspecified 
behavior
lsyncd.c:972: warning: comparison with string literal results in unspecified 
behavior
lsyncd.c: In function ‘one_main’:
lsyncd.c:3049: warning: format ‘%d’ expects type ‘int’, but argument 4 
has type ‘size_t’


--------------------------


Original issue reported on code.google.com by quazardous on 12 Oct 2010 at 7:03

@GoogleCodeExporter
Copy link
Author

I think its safe to say, while this lateral comparisons are a common error, in 
this case it behaves like expected. It checks if its either the default lateral 
(same pointer!) or has been changed and memalloced. I can change the code 
nevertheless to be warning free.

Original comment by axk...@gmail.com on 12 Oct 2010 at 7:23

  • Added labels: Type-Task
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

warning free is always better :p

Original comment by quazardous on 12 Oct 2010 at 9:00

@GoogleCodeExporter
Copy link
Author

fixed it in the svn. I personally didnt get any warnings with -Wall "gcc 
version 4.1.2 20061115", but I changed it nevertheless. Altough the code should 
now be warning free its unfortunally a little less optimal. oh well :)

Original comment by axk...@gmail.com on 12 Oct 2010 at 12:27

@GoogleCodeExporter
Copy link
Author

Original comment by axk...@gmail.com on 27 Nov 2010 at 1:20

  • Changed state: Fixed

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

No branches or pull requests

1 participant