On Tue, Oct 22, 2013 at 8:41 PM, Tong Sun mlist4sunt...@yahoo.com wrote:
Hi,
Is it OK to have compile warnings when building a package? If not,
how can I fix the following:
dial.c: In function 'main':
dial.c:273:8: warning: ignoring return value of 'write', declared with
attribute
To directly answer your question, since I think everyone so far has told
you that you should fix it, this answer from S/O [1]
[...]
[1]
http://stackoverflow.com/questions/3614691/casting-to-void-doesnt-remove-warn-unused-result-error/3615000#3615000
One should note that the question on S/O
Oh yeah, definitely fix it if at all possible ;)
On Wed, Oct 23, 2013 at 10:59 AM, Gert Wollny gw.foss...@gmail.com wrote:
To directly answer your question, since I think everyone so far has told
you that you should fix it, this answer from S/O [1]
[...]
[1]
Gert Wollny gw.foss...@gmail.com writes:
To directly answer your question, since I think everyone so far has told
you that you should fix it, this answer from S/O [1]
[...]
[1]
http://stackoverflow.com/questions/3614691/casting-to-void-doesnt-remove-warn-unused-result-error/3615000#3615000
Hi,
Is it OK to have compile warnings when building a package? If not,
how can I fix the following:
dial.c: In function 'main':
dial.c:273:8: warning: ignoring return value of 'write', declared with
attribute warn_unused_result [-Wunused-result]
write(fd, buf, bufidx);
I got a bunch
On Wed, Oct 23, 2013 at 9:41 AM, Tong Sun wrote:
Is it OK to have compile warnings when building a package? If not,
It is fairly normal to have compile warnings since GCC gets stricter over time.
how can I fix the following:
dial.c: In function 'main':
dial.c:273:8: warning: ignoring
On 22/10/13 18:41, Tong Sun wrote:
Hi,
Is it OK to have compile warnings when building a package?
Although sometimes the compiler is just noisy, I don't like ignoring
compiler warnings. They may be a hint of an omission, a bug, or in the
worst case, a security issue.
I prefer to shut
7 matches
Mail list logo
