[M3devel] building packages from source from cvs -- odbc

[Hendrik Boom]

On Thu, May 17, 2012 at 11:48:37AM -0400, Hendrik Boom wrote:
> On Thu, May 17, 2012 at 06:01:19AM +0000, Jay K wrote:
> > 
> > Good.
> > Wasn't the error message from configure obvious though?
> 
> Evidently not.  Or I was too much asleep last night.  Or I didn't get 
> one. I'm looking for one now.  I find none in my most recent script 
> output.  In one of the old ones I find
> 
> checking for modern makeinfo... no
> configure: WARNING:
> *** Makeinfo is missing or too old.
> *** Info documentation will not be built.
> checking for recent Pod::Man... yes
> 
> but I suspect that may be irrelevant.  Unless packageing fails later 
> because it tries to package the info docs, which I hate anyway.
> 
> No, I don't find any messages.  But then, I'm simply using my old, 
> working cm3 compiler as a bootstrap to build the whole system for the 
> same machine.  I didn't have a specific 'configure' step.
> 
> I found a bunch of compilation warnings about
> * labels and other names  being defined but not used.
> * comparisons always false due to limited range of data type
> * invalid conversion type characters.  Might these actually cause 
> run-time failures?
> * right-hand operand of comma has no effect
> 
> These are unlikely to be the problems I'm contending with, but might 
> it be worth going through the entire build sometime and tracking 
> then all down?  Grepping my script output for "warning" would 
> probably find them all.
> 
> 
> > 
> > 
> > Anyway:
> >   I think there's a "minor" incrementality bug here.   
> >   Incremental build isn't picking back up where it left off/failed.  
> > 
> > Try this:
> >    rm -rf /farhome/hendrik/cm3/cm3/m3-db/odbc/AMD64_LINUX   
> >    rm -rf /tmp/tmp_T7ITL/cm3-all-AMD64_LINUX-d5.9.0-20120516 
> >    ./make-dist.py  
> 
> Will do.  I had planned to do something like this when I was awake this 
> morning, but I was unsure just which files needed to be deleted.
> 

It definitely got past odbc now.  But it stopped within ESC.  I was 
surprised to find it her; I had thought the source code to be long lost.
I don't see am error message except for the failure to find .M3EXPORTS, 
ahich is probably something that cm3 should have generated.

The m3makefile 
/farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/src/m3makefile
seems to have trouble finding 
/tmp/tmpua41ba/cm3-all-AMD64_LINUX-d5.9.0-20120517/pkg/prover/AMD64_LINUX/.M3EXPORTS
which seems to me to be one level out in the source code.  Just what 
determines the order that these things are to be compiled?  The 
compilation log makes it look as if the outer one (prover) needed to be 
compiled first, so as to enerate the .M3EXPORTS file, but that the inner 
one (prover/test) actually got compiled first. 

Here's the output, starting with the first line of log contianing either 
the words "Simplify" or "prover".


== package /farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test ==

 +++ /tmp/tmpua41ba/cm3-all-AMD64_LINUX-d5.9.0-20120517/bin/cm3    
-build -DROOT=/farhome/hendrik/cm3/cm3 +++
--- building in AMD64_LINUX ---

ignoring ../src/m3overrides

"/farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/src/m3makefile", line 
1: quake runtime error: unable to open 
"/tmp/tmpua41ba/cm3-all-AMD64_LINUX-d5.9.0-20120517/pkg/prover/AMD64_LINUX/.M3EXPORTS" 
for reading

--procedure--  -line-  -file---
import             --  <builtin>
include_dir         1  
/farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/src/m3makefile
                    5  
/farhome/hendrik/cm3/cm3/ESC/Simplify/prover/test/AMD64_LINUX/m3make.args

Fatal Error: package build failed
 *** execution of [<function _BuildGlobalFunction at 0x10d0de8>, 
<function _ShipFunction at 0x10d0c80>] failed ***
hendrik at april:~/cm3/cm3/scripts/python$ exit

-- hendrik