>
> At 1:43 PM +0200 2001-06-22, Erik Mouw wrote:
> >On Thu, Jun 21, 2001 at 10:30:40PM -0400, Rick Hohensee wrote:
> >> Why does Linux have a mktime routine fully coded in linux/time.h that
> >> conflicts directly with the ANSI C standard library routine of the same
> >> name? It breaks a cou
At 1:43 PM +0200 2001-06-22, Erik Mouw wrote:
>On Thu, Jun 21, 2001 at 10:30:40PM -0400, Rick Hohensee wrote:
>> Why does Linux have a mktime routine fully coded in linux/time.h that
>> conflicts directly with the ANSI C standard library routine of the same
>> name? It breaks a couple things ag
On Thu, Jun 21, 2001 at 10:30:40PM -0400, Rick Hohensee wrote:
> Why does Linux have a mktime routine fully coded in linux/time.h that
> conflicts directly with the ANSI C standard library routine of the same
> name? It breaks a couple things against libc5, including gcc 3.0. OK, you
> don't care
Why does Linux have a mktime routine fully coded in linux/time.h that
conflicts directly with the ANSI C standard library routine of the same
name? It breaks a couple things against libc5, including gcc 3.0. OK, you
don't care about libc5. It's still pretty weird. Wierd? Weird.
Rick Hohensee
www.
4 matches
Mail list logo