[Info-Ingres] IJ: Problem building release

Martin Bowes martin.bowes at ctsu.ox.ac.uk
Tue Nov 13 03:08:40 CST 2007


Hi Robert,

Yep it was the missing pax that caused the problem.

I'd gutted the build area to look at an issue and make sure nothing from
the prior monkeying-around would survive. I just forgot to reinstall the
pax and xerces stuff. Whoops.

Marty

-----Original Message-----
From: info-ingres-bounces at kettleriverconsulting.com
[mailto:info-ingres-bounces at kettleriverconsulting.com] On Behalf Of
Robert Bonchik
Sent: 12 November 2007 21:12
To: info-ingres at kettleriverconsulting.com
Subject: Re: [Info-Ingres] IJ: Problem building release

In article <mailman.55.1194619597.18164.info-
ingres at kettleriverconsulting.com>, you say...
> I'm trying to build my latest release of Opensource and have suddely
> come across the following...
> 
> Errors on building release...
> 
>   Computing archive checksum... 
> 
>  
> 
> Problems computing checksum for:
>
/home/ingdev/SandBox/Ingres2006rls2/release/rMVB_tups/basic/install.pgz

The code to perform the checksum is called from buildrel.c where it 
calls function ip_file_info_comp() in ipfile.c
The code is very simple and only exits with an error if the file is not 
found.

If the file .../release/rMVB_tups/basic/install.pgz is not found then 
that means that the archive program fails or is not found.  On Linux the

archive program is 'pax', on other unix platforms it is 'tar'.
On Linux the 'pax' executable must exist at $ING_BUILD/bin/pax
Do you have a version of 'pax' in the $ING_BUILD/bin directory?

The 'pax' executable is copied to the $ING_BUILD/bin directory during 
the jam build process by using the PAXLOC variable that you defined to 
locate the version of 'pax' that you built or are supplying for this 
build.  If you did not set the PAXLOC variable properly you would get an

error during the jam build and it would tell you that some targets 
failed to build.  Did you get any errors during the jam build that said 
that it did not know how to build 'pax'?

If 'pax' does exist in the $ING_BUILD/bin directory, then have you 
checked to determine if it actually works?

These are the most likely causes of your problem.

Robert
_______________________________________________
Info-Ingres mailing list
Info-Ingres at kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres



More information about the Info-Ingres mailing list