<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'>
I have not built the entire tree since that stuff came in.<BR>Oops.<BR> <BR> <BR>If the goal is to get some sort of .deb, to see what it is, to give it to someone else, do this:<BR> <BR> <BR> cd scripts <BR> rm PKGSDB <BR> edit down pkginfo.txt <BR> <BR> hm, oops, this stuff isn't in there? <BR> <BR> <BR> The same information might be duplicated in pylib.py? <BR> I think I fixed that..based on a quick read. <BR> <BR> <BR> Maybe we pickup all m3makefiles? Maybe. <BR> Just rm -rf from your tree anything that is giving you trouble now, as you've already built lots of stuff. <BR> <BR> <BR> - Jay<br><br> <BR><div><div id="SkyDrivePlaceholder"></div>> Date: Thu, 17 May 2012 14:57:53 -0400<br>> From: hendrik@topoi.pooq.com<br>> To: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] building packages from source from cvs -- odbc<br>> <br>> On Thu, May 17, 2012 at 11:48:37AM -0400, Hendrik Boom wrote:<br>> > On Thu, May 17, 2012 at 06:01:19AM +0000, Jay K wrote:<br>> > > <br>> > > Good.<br>> > > Wasn't the error message from configure obvious though?<br>> > <br>> > Evidently not. Or I was too much asleep last night. Or I didn't get <br>> > one. I'm looking for one now. I find none in my most recent script <br>> > output. In one of the old ones I find<br>> > <br>> > checking for modern makeinfo... no<br>> > configure: WARNING:<br>> > *** Makeinfo is missing or too old.<br>> > *** Info documentation will not be built.<br>> > checking for recent Pod::Man... yes<br>> > <br>> > but I suspect that may be irrelevant. Unless packageing fails later <br>> > because it tries to package the info docs, which I hate anyway.<br>> > <br>> > No, I don't find any messages. But then, I'm simply using my old, <br>> > working cm3 compiler as a bootstrap to build the whole system for the <br>> > same machine. I didn't have a specific 'configure' step.<br>> > <br>> > I found a bunch of compilation warnings about<br>> > * labels and other names being defined but not used.<br>> > * comparisons always false due to limited range of data type<br>> > * invalid conversion type characters. Might these actually cause <br>> > run-time failures?<br>> > * right-hand operand of comma has no effect<br>> > <br>> > These are unlikely to be the problems I'm contending with, but might <br>> > it be worth going through the entire build sometime and tracking <br>> > then all down? Grepping my script output for "warning" would <br>> > probably find them all.<br>> > <br>> > <br>> > > <br>> > > <br>> > > Anyway:<br>> > > I think there's a "minor" incrementality bug here. <br>> > > Incremental build isn't picking back up where it left off/failed. <br>> > > <br>> > > Try this:<br>> > > rm -rf /farhome/hendrik/cm3/cm3/m3-db/odbc/AMD64_LINUX <br>> > > rm -rf /tmp/tmp_T7ITL/cm3-all-AMD64_LINUX-d5.9.0-20120516 <br>> > > ./make-dist.py <br>> > <br>> > Will do. I had planned to do something like this when I was awake this <br>> > morning, but I was unsure just which files needed to be deleted.<br>> > <br>> <br>> It definitely got past odbc now. But it stopped within ESC. I was <br>> surprised to find it her; I had thought the source code to be long lost.<br>> I don't see am error message except for the failure to find .M3EXPORTS, <br>> ahich is probably something that cm3 should have generated.<br>> <br>> The m3makefile <br>> /farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/src/m3makefile<br>> seems to have trouble finding <br>> /tmp/tmpua41ba/cm3-all-AMD64_LINUX-d5.9.0-20120517/pkg/prover/AMD64_LINUX/.M3EXPORTS<br>> which seems to me to be one level out in the source code. Just what <br>> determines the order that these things are to be compiled? The <br>> compilation log makes it look as if the outer one (prover) needed to be <br>> compiled first, so as to enerate the .M3EXPORTS file, but that the inner <br>> one (prover/test) actually got compiled first. <br>> <br>> Here's the output, starting with the first line of log contianing either <br>> the words "Simplify" or "prover".<br>> <br>> <br>> == package /farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test ==<br>> <br>> +++ /tmp/tmpua41ba/cm3-all-AMD64_LINUX-d5.9.0-20120517/bin/cm3 <br>> -build -DROOT=/farhome/hendrik/cm3/cm3 +++<br>> --- building in AMD64_LINUX ---<br>> <br>> ignoring ../src/m3overrides<br>> <br>> "/farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/src/m3makefile", line <br>> 1: quake runtime error: unable to open <br>> "/tmp/tmpua41ba/cm3-all-AMD64_LINUX-d5.9.0-20120517/pkg/prover/AMD64_LINUX/.M3EXPORTS" <br>> for reading<br>> <br>> --procedure-- -line- -file---<br>> import -- <builtin><br>> include_dir 1 <br>> /farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/src/m3makefile<br>> 5 <br>> /farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/AMD64_LINUX/m3make.args<br>> <br>> Fatal Error: package build failed<br>> *** execution of [<function _BuildGlobalFunction at 0x10d0de8>, <br>> <function _ShipFunction at 0x10d0c80>] failed ***<br>> hendrik@april:~/cm3/cm3/scripts/python$ exit<br>> <br>> -- hendrik<br>> <br></div> </div></body>
</html>