[M3devel] Success with libXaw.so.7, but more help needed.

[Jay K]

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