Re: [MiNT] Still don't get it - difference between 68020 and 68020-60

[Paul Wratt <paul.wratt@gmail.com>]

development machines will always be bloated, 112mb is reasonable,
especially considering how much is used in a windows or linux
environment.

That said, the 112mb is for the complete gcc+libs for ALL cpu/fpu
combinations, not for a particular installation with full multilib
capabilities (right?)

This sort of multi-version installation implies that the SpareMiNT RPM
distro should contain various branches or trees (like most other
repos), even if it is just for MiNT kernel, XaAES, GCC, LIBgcc, etc.

Even if this is not explicitly the case, the various versions does
affect things like the updater Jo Even has been working on.

Essentially this is the last chance we will get to provide a full
68000 system, even with the 14mb ram board, current versions of GCC
are at about the extreme limit of that hardware, and its only going to
get worse

We will always need/require base 68000 libs etc for various reasons,
but they may become unusable on 68000 hardware as packages are
continually updated.

>From posts on the list, it appears (for SpareMiNT at least) there are
m68000, m68020-60 & v4e versions of most packages. Is this the case
with all available packages being built (Keith, Mark, Mono, etc ?)

With these multilib packages, a set of multilib ./configure, make &
RPM files and scipts should be made available as a base MiNT project
skeleton, even if this is the same set as used for a build farm

The last question raised, with a full set of multilib gcc for v4e
machines, is this enough to produce m68000 & m68020-60, etc, or is the
a need for a cross compiler version of gcc

Finally, the task of building a build farm. Are the current systems up
to the task? With the main servers in the states and the volume of
(potential) packages, is there a need for a european/uk, eastern
block/polish and australiasian/asian mirrors?

Obviously some of Alans work in providing the same or similar build
sets for Gentoo MiNT will help and assist in cobbling together
something like  a SpareMiNT build Farm.

Even if a full set of multilib packages are NOT maintained over time,
it would be good to start with a thorough set, something that would
also be useful when distributed on CD/DVD (not knowing the target
hardware)

Food for thought

Paul