On Sat, 24 Nov 2012, Anthony G. Basile wrote:
> From: "Anthony G. Basile"
>
> stime and utime are declared __u64 but are never used. On a glibc system
> this is harmless lint, but on a uClibc system, because of the difference
> in they way header files stack, including stdio.h brings in time.h
On Sat, 24 Nov 2012, Anthony G. Basile wrote:
From: Anthony G. Basile bas...@opensource.dyc.edu
stime and utime are declared __u64 but are never used. On a glibc system
this is harmless lint, but on a uClibc system, because of the difference
in they way header files stack, including
On Sat, 24 Nov 2012, Anthony G. Basile wrote:
> From: "Anthony G. Basile"
>
> stime and utime are declared __u64 but are never used. On a glibc system
> this is harmless lint, but on a uClibc system, because of the difference
> in they way header files stack, including stdio.h brings in time.h
On Sat, 24 Nov 2012, Anthony G. Basile wrote:
From: Anthony G. Basile bas...@opensource.dyc.edu
stime and utime are declared __u64 but are never used. On a glibc system
this is harmless lint, but on a uClibc system, because of the difference
in they way header files stack, including
From: "Anthony G. Basile"
stime and utime are declared __u64 but are never used. On a glibc system
this is harmless lint, but on a uClibc system, because of the difference
in they way header files stack, including stdio.h brings in time.h and
this causes a name collision with stime. Since
From: Anthony G. Basile bas...@opensource.dyc.edu
stime and utime are declared __u64 but are never used. On a glibc system
this is harmless lint, but on a uClibc system, because of the difference
in they way header files stack, including stdio.h brings in time.h and
this causes a name collision
6 matches
Mail list logo
