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