2016-11-29 37 views
2

我得到一对警告用glibc 2.22版本:我可以通过glibc安全地忽略这些pthread警告吗?

In file included from /net/module/sw/glibc/2.22/include/pthread.h:23:0, 
       from foo.h:48, 
       from foo.c:23: 
/net/module/sw/glibc/2.22/include/sched.h:74:57: warning: ‘struct timespec’ declared inside parameter list 
extern int sched_rr_get_interval (__pid_t __pid, struct timespec *__t) __THROW; 
                 ^
/net/module/sw/glibc/2.22/include/sched.h:74:57: warning: its scope is only this definition or declaration, which is probably not what you want 
In file included from foo.h:48:0, 
       from foo.c:23: 
/net/module/sw/glibc/2.22/include/pthread.h:1002:21: warning: ‘struct timespec’ declared inside parameter list 
     const struct timespec *__restrict __abstime) 
        ^

和:

In file included from /net/module/sw/glibc/2.22/include/sys/param.h:26:0, 
       from foo.h:51, 
       from foo.c:23: 
/net/module/sw/glibc/2.22/include/limits.h:123:3: warning: #include_next is a GCC extension 
# include_next <limits.h> 
^

我使用GCC 5.3.0这个版本的glibc。

由于这些警告是引用外部库,我不控制,如果我的应用程序似乎通过测试,我可以安全地忽略这些警告吗?

我担心的是,这些警告(尤其是有关pthread)可能表明引入微妙的错误的,我没有测试,以赶上。

回答

0

是,这些警告应该是无害的,但struct timespec警告肯定是奇数。通常,他们会被GCC对系统头文件的警告抑制所掩盖。

相关问题