[M3devel] problem building packages -- preliminary analysis.

Jay K jay.krell at cornell.edu
Wed May 16 22:24:52 CEST 2012


Your CVS tree is maybe incomplete or out of date? Try this:
   cd m3-sys   
   rm -rf m3cc  
   cvs -z3 upd -dAP m3cc   
   cd m3cc   
   cm3  
 

Or just checkout a whole new tree.


Yes, there is a lot of C code, that uses autoconf -- the gcc backend.


 - Jay

> Date: Wed, 16 May 2012 12:59:27 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: [M3devel] problem building packages -- preliminary analysis.
> 
> On Wed, May 16, 2012 at 11:26:35AM -0400, Hendrik Boom wrote:
> > On Wed, May 16, 2012 at 10:56:53AM -0400, Hendrik Boom wrote:
> > > On Tue, May 15, 2012 at 10:33:12PM +0000, Jay K wrote, and hendrik reformatted:
> > 
> > So this is what I did:
> > > 
> > > >
> > > >  If you already have a working cm3 on the system you want to run it on
> > > 
> > > Which is what I've got on my two machines, so this is what I'll be 
> > > trying.
> > > 
> > > >     cd scripts/python
> > > >     ./upgrade.py
> > 
> > It ran for a while, conpiling some Modula 3 stuff and apparently a lot 
> > of C code (this part seemed to use autoconf tools), and then stopped 
> > with
> > 
> > cd . && cd libcpp && make  CFLAGS="-g -O2"   MAKE=make  AUTOCONF=: 
> > AUTOMAKE=: LEX='touch lex.yy.c' MAKEINFO=: libcpp.a | tee -a 
> > /farhome/hendrik/cm3/src-all/m3-sys/m3cc/src/../AMD64_LINUX/_m3.log
> > /bin/sh: line 0: cd: libcpp: No such file or directory
> > "/farhome/hendrik/cm3/src-all/m3-sys/m3cc/src/m3makefile", line 312: 
> > quake runtime error: exit 1: cd . && cd libcpp && make  CFLAGS="-g -O2"   
> > MAKE=make  AUTOCONF=: AUTOMAKE=: LEX='touch lex.yy.c' MAKEINFO=: 
> > libcpp.a | tee -a 
> > /farhome/hendrik/cm3/src-all/m3-sys/m3cc/src/../AMD64_LINUX/_m3.log
> > 
> > --procedure--  -line-  -file---
> > exec               --  <builtin>
> > m3cc_Run          312  
> > /farhome/hendrik/cm3/src-all/m3-sys/m3cc/src/m3makefile
> > include_dir       586  
> > /farhome/hendrik/cm3/src-all/m3-sys/m3cc/src/m3makefile
> >                     8  
> > /farhome/hendrik/cm3/src-all/m3-sys/m3cc/AMD64_LINUX/m3make.args
> > 
> > Fatal Error: package build failed
> >  *** execution of [<function _BuildGlobalFunction at 0x7f298eea9050>, 
> > <function _ShipFunction at 0x7f298eea90c8>] failed ***
> > hendrik at april:~/cm3/src-all/scripts/python$ 
> 
> Looking at the python code in src-all/m3-sys/m3cc/src/m3makefile, I 
> find line 586:
> 
> m3cc_Run (["cd " & build_dir & " && cd libcpp && " & M3CC_MAKE & " 
> libcpp.a | tee -a " & Log])
> 
> Now seeng what appears to be the actual command line in the error 
> message: 
> 
> cd . && cd libcpp && make  CFLAGS="-g -O2" MAKE=make  AUTOCONF=: AUTOMAKE=: LEX='touch lex.yy.c' MAKEINFO=: libcpp.a | tee -a
> 
> it appears that the variable bild_dir has the value "."
> 
> At some time, "." probably was the build directory.  But at the moment 
> we execute this command, I suspect the build dir is actually 
> /farhome/hendrik/cm3/src-all/m3-sys/m3cc/AMD64_LINUX/
> 
> since a recent message was 
> 
> make[1]: Leaving directory 
> `/farhome/hendrik/cm3/src-all/m3-sys/m3cc/AMD64_LINUX/libdecnumber'
> 
> There is no libcpp directory there.  locate tells me there are libcpp 
> directories at
> src-all/m3-sys/m3cc/gcc-apple/libcpp
> 
> and
> 
> src-all/m3-sys/m3cc/gcc/libcpp
> 
> and that's about it.  (yes, I reran locatedb to make sure it was up to 
> date).
> 
> Could it be that the build_dir variable should contain an absolute 
> rather than a relative path?
> 
> Or should I rerun everything using scipt to generate a huge log?
> 
> -- hendrik
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120516/7dd134ed/attachment-0002.html>


More information about the M3devel mailing list