On Fri, Oct 16, 1998 at 06:26:38PM +1000, Stuart Lamble wrote:
> Doing things this way would entail a new source package each time a
> new architecture is bootstrapped. Probably the cleanest way overall,
> though, when all's said and done.. and no doubt Guy (or whoever's
> currently maintaining th
On Fri, Oct 16, 1998 at 06:26:38PM +1000, Stuart Lamble wrote:
> > On Sat, Oct 10, 1998 at 01:56:06PM +1000, Stuart Lamble wrote:
> >
> > Couldn't you extract the arch dep parts in different subdirectories and move
> > them to the correct place in the debian/rules file just before building?
> > So
> On Sat, Oct 10, 1998 at 01:56:06PM +1000, Stuart Lamble wrote:
> >
> > The bootstrap compiler is distributed (mostly) as assembler
> > source, so they're clearly platform dependant. The sources
> > for the rest of the system are distributed as Modula 3 source
> > code, so they're clearly platfor
On Sat, Oct 10, 1998 at 01:56:06PM +1000, Stuart Lamble wrote:
>
> The bootstrap compiler is distributed (mostly) as assembler
> source, so they're clearly platform dependant. The sources
> for the rest of the system are distributed as Modula 3 source
> code, so they're clearly platform _in_depend
Simple (conceptually) problem:
I'm working on packaging the pm3 Modula 3 distribution for
Debian, and have run into a problem. There are two tarballs
that are available for this: the bootstrap compiler, and the
sources for the rest of the system. Once M3 is up and running,
you can generate a boots
5 matches
Mail list logo
