[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] What's in, what's out?
- To: mint@fishpool.com (MiNT mailing list)
- Subject: Re: [MiNT] What's in, what's out?
- From: Guido Flohr <gufl0000@stud.uni-sb.de>
- Date: Mon, 29 Nov 1999 01:42:53 +0100
- In-reply-to: <Pine.MNT.4.10.9911281211580.193-100000@rakas>; from Martin-Eric Racine on Sun, Nov 28, 1999 at 12:23:15PM +0200
- Mail-followup-to: mint@fishpool.com (MiNT mailing list)
- References: <19991128032222.F37@stud> <Pine.MNT.4.10.9911281211580.193-100000@rakas>
- Sender: owner-mint@fishpool.com
On Sun, Nov 28, 1999 at 12:23:15PM +0200, Martin-Eric Racine wrote:
> On 28.11.1999, Guido Flohr <gufl0000@stud.uni-sb.de> wrote:
>
> > > On 25.11.1999, Guido Flohr <gufl0000@stud.uni-sb.de> wrote:
> > >
> > > > Source-compatibility is a very important issue for me.
> > >
> > > Me too, but not at the expense of breaking documented features.
> >
> > Yeah! Good point! Which features?
>
> The Atari Compendium, GEMDOS conmpatibility.
Which GEMDOS features are not supported by MiNT? More important: Which
MiNT features are not supported any more by the current kernel?
No, "the bible" is not an answer.
> > > Currently, the lib produces broken binaries that die with a
> > > bus error, even with an indecently huge malloc in the header,
> > > most of the time. Only really simple apps work.
> >
> > Please never ask me again for developer sources. You have downloaded a
> > developer source tree that produces broken binaries. Correct.
>
> I'm talking about 0.53, btw. The current development beta is
> much better. Nonetheless, any _lib_ since 0.49 produces unstable
> binaries.
Attention folks: Don't install anything from Sparemint. All binaries there
are unstable.
> > Remember my words: "One of these two patches *may* work".
>
> And it indeed succeeded in getting the lib to compile but, as
> with previous versions, still produces unstable binaries.
Not here. Not at Frank's. Not at Edgar's.
Maybe have a look at your setup.
> Btw, since it apparently hit a nerve, unintentionally, let me
> state one thing clearly:
It apparently did.
And it's not the first time that that happened to you "unintentionally".
> The above statement was merely an observation that the current
> GCC, libs and binary tools are not yet stable e.g. it's not yet a
> "unpack and use" environment, because even simple binaries do not
> compile to something stable.
The MiNTLib and the binutils from Sparemint *are* unpack and use. And I
think that this is the first time that something like that is available
for MiNT.
gcc is not yet ready but you will allow us to finish it first?
Ciao
Guido
--
http://stud.uni-sb.de/~gufl0000/
mailto:guido@atari.org