[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] du bug

To: MiNT mailing list <mint@fishpool.com>
Subject: Re: [MiNT] du bug
From: "Guido Flohr" <gufl0000@stud.uni-sb.de>
Date: Thu, 11 May 2000 00:24:39 +0200
In-reply-to: <200005101918.VAA27048@hawking.suse.de>; from schwab@suse.de on Wed, May 10, 2000 at 09:18:06PM +0200
Mail-followup-to: MiNT mailing list <mint@fishpool.com>
References: <20000418171941.A25087@hrzpub.tu-darmstadt.de> <Pine.MNT.4.10.10004181732210.219-100000@FreeMiNT.st.uni-magdeburg.de> <20000419022459.F1115@zowee.kosmos.all> <200005101918.VAA27048@hawking.suse.de>
Reply-to: guido@freemint.de
Sender: owner-mint@fishpool.com

On Wed, May 10, 2000 at 09:18:06PM +0200, Andreas Schwab wrote:
> "Guido Flohr" <gufl0000@stud.uni-sb.de> writes:
> 
> |> I think there should be an update for the MiNTLib anyway.  By accident
> |> __time_t is currently defined as __int32_t instead of long in
> |> <bits/types.h>.  Not really a bug but at least mgetty (and probably
> |> others) assume that time_t is long, not int.
> 
> Then mgetty is broken.  time_t can be any (arithmetic) type.

Sure, but a lot of code is broken in that respect and it turned out to be
unwise to insist on standard conformance ...

Mgetty is not the only software that silently expects certain data types
to have a certain size or to be signed/unsigned where the 
standard merely asks for any arithmetic type.  Unfortunately, any
deviation from Linux implementations is asking for trouble nowadays.  Some
people simply don't like autoconf.

Ciao

Guido
-- 
http://www.stud.uni-saarland.de/
Send your spam to president@whitehouse.gov and your replies to
mailto:guido at freemint dot de

References:
- Re: [MiNT] du bug
  - From: Andreas Schwab <schwab@suse.de>

Prev by Date: Re: [MiNT] 1.15.8b kernel
Next by Date: Re: [MiNT] MiNT and MetaDOS
Previous by thread: Re: [MiNT] du bug
Next by thread: [MiNT] MiNT lib 55
Index(es):
- Date
- Thread