Packaging of Modula-3 Linux/Alpha port
On Sat, 7 Feb 1998 dragisha@frodo.ho.com wrote:
> > On Sat, 7 Feb 1998 dragisha@frodo.ho.com wrote:
> > > It works. :)
> >
> > You mean you were able to compile a working CVSup and CVSupd ?
>
> cvsup, yes, cvsupd too, but I tested cvsup much more than cvsupd as it is
> a lot easier for setup :).
> >
> > > With @M3nepreemption, but it is functional as there are other
> > > means for thread switching which ensure working threads :).
> >
> > Which are ? (Bear with me I do not know the M3 internals as you do)
>
> IMHO, threads are switched when running thread decides to return control
> to scheduler. It is not perfect, as sometimes there will be forever-running
> thread or one taking too much time, but as you said, first generation is
> first generation :).
>
> Some return control points are waiting on I/O, delaying and (I am not 100%
> sure in this) end of LOCK statement. LOCK statements are good (not perfect
> of course) regulator ;). Here is output in cvsup debugging session..
>
> (m3gdb) threads
> -id- -Thread.T- -state-
> 4 16_1202836d8 alive
> 3 16_12027c5c8 alive
> 2 16_1202714d0 waiting until {tv_sec = 886815586, tv_usec = 570312}
> 1 16_120262008 alive
> 5 16_120283a98 waiting for I/O
>
> Working compiler and cvsup are proving this as working to some extent.
> Mentor does not work, as it is heavy multithreaded. Columns is only app that
> does not compile because of some bug in back_end. And so on...
>
> > > Problem is, shared libraries don't work, and there are few other tiny
> > > annoyances.
> >
> > For the first generation it shouldn't be much of a problem.
>
> Of course, for me it is important to clean out runtime.
>
> >
> > > Funny thing, at first I ported some pre-3.6 release, thinking all time it
> > > is 3.6 and wondering where are few things. After switching to 3.6 (and
> > > re-porting it) I learned about missing m3export dir in m3.tar.gz. Dropped.
> > > Luckily, one from 3.5 worked :).
> >
> > :-)
> >
> > > What is best way for you to start with this thing? There is no any
> > > packaging yet, I will try to get one of my coworkers to add automatic
> > > .rpm-ing to templates.
> >
> > I´d strongly recommend that you start with packaging it as a .deb (Debian)
> > first. The .deb Format is a superset of the .rpm format and there are
> > tools which will do an automatic conversion from .deb to .rpm and
> > .tar(.gz) for you.
>
> Problem is, my company is RedHat only :). We do not have any Debian CDs
> and it is not so easy to get it here. But, we will try to find needed tools
> on Internet.
>
> Automatic packaging is one of goals here. I would like to have template
> which builds relocatable packages.
I think it shouldn't be a problem to get you a CD of the upcoming
Debian 2.0.
Any volunteers that can cut him a CD so that create Debian Packages of
Modula-3 with glibc and gcc-2.8 based backend ?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: