MiNT 1.11 problems

["Nicholas S Castellano" <entropy@terminator.rs.itd.umich.edu>]

>I use gcc 2.3.3 to compile MiNT, and haven't had any problems running
>MultiTOS. The library version should not matter at all; if it does,
>then this represents either a serious bug in MiNT or one in the libraries.
>(In fact MiNT uses only a very few, very basic library functions.)
>I suppose it's time to remove all the remaining library calls from MiNT;
>that would at least eliminate one variable.

If changing the compiler used to compile MiNT fixes the problem, it
isn't likely that the library has anything to do with it.  Unless of
course the libs are also recompiled with the same compiler.  No one
has mentioned anything about having done that or not, though.
Currently, the kernel only uses 3 or 4 library functions...things like
memcpy, bcopy, and so on...and these functions are all quite stable.

Has anyone that has been having problems with GCC-2.5.8 and MultiAES
tried compiling a kernel with optimization disabled?

I'd love to be of some help in tracking this down, but I don't have
MultiAES.  My MiNT 1.11 kernel seems to be running fine (compiled with
gcc-2.5.8 -DDEBUG_INFO -DMULTITOS -DONLY_030 with full optimization)
on my TT with the normal AES.  But then again, I haven't used any GEM
software in so long that I've almost forgotten what the desktop looks
like. 

Cheers,
entropy

--
entropy -- it's not just a good idea, it's the second law.
Personal mail:      entropy@gnu.ai.mit.edu
MiNT library mail:  entropy@terminator.rs.itd.umich.edu
"what do you have against octal?" -jrb