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

Re: MiNT cross-compiler



Thorsten Glaser wrote:
I thought you’d appreciate a progress mail.

Hello, Thorsten.

Thanks for these nice news!

On my side, I'm just back from vacation. Meanwhile, I got the FSF agreements for the binutils and GCC. Same for Guido Flohr, the original author of the binutils patch. So I'm ready to start working on the binutils mailing list to get most of the MiNT patch committed. I plan to rework the patches in the light of your own work, to be sure we only do the necessary changes, no more. When the binutils is finished, I will do the same for GCC, including your changes, of course. Well, that's my roadmap. That will certainly take some time, but it does not matter.

After that, the Debian specific patches should be very minimal.

For now, I’ve built binutils and gcc-4.6 with your patches (applied
liberally rather than literally as I mailed you)

Good. My patches are written exactly in that spirit: that works for me, take what you want for your own needs.

and got the dpkg maintainer to add mint-m68k as a Debian architecture
(patch also applied locally).

Very good.

I’ve built gcc-4.6 as a DEB_STAGE=stage1 compiler,
that is, without a C library or header files, but self-contained.

BTW, that stage1 compiler could be used to compile the emutos package. EmuTOS is a Free ROM for Atari compatible computers (compatible with the original OS) and is shipped in binary form inside Debian's aranym and hatari packages. EmuTOS does not use external libraries (except libgcc).

For now I’m doing without mintlib; my next step is to see whether
that is actually enough to build atari-bootstrap

I don't know what are the contents of that Debian atari-bootstrap package, so I don't know either.

(I looked at your packages, but would prefer to do things in
a more Debian way. No criticism, for a private repository they are
good enough.)

Sure. My first goal was to get a working cross-compiler, whatever the method. Now it has proven to work very well, so the next step is to industrialize the build process, what you are doing.

This will take me some time, though; the m68k work has “idle priority”
for me, i.e. I’m doing it when nothing else pops up, and to educate
myself further (about m68k, Debian, porting, and other unixoid OSes).

Same for me. I had very few free time lately, but I would be very happy to clean up all that stuff and get everything committed.

What is PML? Your page only mentions a link to ftp.funet.fi which
is pretty much saying nothing.

PML is the Portable Math Library. Normally the MiNT toolchain use fdlibm as libm, but when I started working on GCC I wasn't aware of it. Today PML is reliable enough for my needs (including 68881 and ColdFire), so there is no hurry for me to switch to fdlibm.

Unfortunately, at the current time I do not know whether the climate
in Debian would be welcoming to a full FreeMiNT (cross-built) develop-
ment suite (there is precedent for a MinGW one though).

This is the big question.
I also wonder if the FSF people will welcome the m68k-atari-mint target which still use the obsolete a.out format for object files and executables.

But independent of that, my changes (especially the dpkg one) would help people
reactivating “Debian GNU/MiNT”

Sure, that will certainly help a lot.

So many thanks for all the work you made so far, there is still much to do.

--
Vincent Rivière


Reply to: