<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
You might as well just use something in scripts to rebuild the entire system.<BR>It isn't so difficult nor takes very long.<BR> <BR> <BR> Get a working cm3 on any system. <BR> cd scripts/python <BR> ./boot1.py <target-such-as-I386_LINUX> <BR> That will produce a "bootstrap" archive. <BR> Copy it to the "new" system. <BR> Extract it. <BR> Cd into it. <BR> Look at the top of Makefile and see if it seems reasonable (we should use autoconf here). <BR> run make. <BR> That should give you a working cm3 for the new system. <BR> Put that on path, e.g.:<BR> su <BR> rm -rf /usr/local/cm3<BR> mkdir -p /usr/local/cm3/bin <BR> cp cm3 /usr/local/cm3/bin <BR> exit <BR> PATH=/usr/local/cm3/bin:$PATH <BR> cd to scripts/python in the source tree on the new system.<BR> Then run ./boot2.sh <BR> Then ./make-dist.py. <BR> <BR> <BR>That should give you the entire system newly built, and a .deb.<BR> <BR> <BR>If you already have a working cm3 on the system you want to run it on<BR> cd scripts/python <BR> ./upgrade.py <BR> ./make-dist.py <BR> <BR> <BR>I'd really like to get to the point of:<BR> extract <BR> ./configure <BR> make <BR> make install or make deb <BR> <BR> <BR>To make this work how people really want, we have to have a C-generating backend.<BR>Or else provide binary packages for "every" system, which isn't viable.<BR> <BR> <BR> <BR>If Linux distributions took binary compatibility seriously, we wouldn't have this problem.<BR>They seem to encourage/require rebuilds for every revision.<BR>But surely this is not true, as there exist some closed source products like Adobe Acrobat?<BR>There is no such problem on Windows, nor I suspect Solaris, nor hypothetically on Irix, AIX, VMS, HP-UX, Tru64, etc.<BR> <BR> <BR> - Jay<br><BR><div><div id="SkyDrivePlaceholder"></div>> Date: Tue, 15 May 2012 11:12:18 -0400<br>> From: hendrik@topoi.pooq.com<br>> To: m3devel@elegosoft.com<br>> Subject: [M3devel] Success with libXaw.so.7, but more help needed.<br>> <br>> I got it to recognise libXaw.se.7.<br>> <br>> I downloaded and untarred the src-all archive.<br>> <br>> I used cm3 to compile and ship several libraries:<br>> <br>> m3-ui/formsvbt<br>> m3-ui/videovbt<br>> m3-ui/vbtkit<br>> m3-ui/ui<br>> m3-ui/X11R4<br>> <br>> Each one was simple, like<br>> cd formsvbt<br>> cm3<br>> cm3 -ship<br>> <br>> I identified the libraries that needed recompilation fron the <br>> compilation error messages I got whein compiling the program I was <br>> originally trying to work on. A message like:<br>> <br>> /usr/bin/ld: warning: libXaw.so.6, needed by /usr/local/cm3/pkg/vbtkit/AMD64_LINUX/libm3vbtkit.so, not found (try using -rpath or -rpath-link)<br>> <br>> indicated recompiling m3-ui/vbtkit (I had to look around in src-all too <br>> figure out the m3-ui part).<br>> <br>> At least these libraries work now. So my immediate objective is <br>> accomplished.<br>> <br>> But the job is not done. This is simply too much to inflict on an <br>> inexperienced beginner. He'd pretty well have to desperately want to <br>> use Modula 3 to go to all this trouble AND have the advice of an <br>> experienced Modula 3 user (such as me, and I had trouble!) to get this <br>> far.<br>> <br>> The next steps, which I *will* need help with if I am to do them, are:<br>> <br>> figure out which other libraries have similar obsolete dependencies.<br>> <br>> recompile them<br>> <br>> Prepare new distribution archives and a new .deb file, suitably <br>> annotated as to which Debian release they work with.<br>> <br>> The .deb is surely the easiest way for a beginner to install Modula 3 on <br>> Debian.<br>> <br>> Make the .deb spread its contents over the file system, as required for <br>> it to be accepted into Debian again. Modula 3 has been absent from <br>> Debian for far too long.<br>> <br>> -- hendrik<br></div> </div></body>
</html>