<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
A good option is to export these three variables:<BR>
<BR>
CM3VERSIONNUM <BR> CM3VERSION<BR> CM3LASTCHANGED<BR><BR>
and/or use the -D switches.<BR>
Otherwise m3-sys/cm3/m3makefile goes down a gnarly path (that I put in) of trying to read scripts/version.<BR>
Which usually works, but could be too sensitive to /bin/sh behavior...often bites us you know.<BR>
<BR>
- Jay<BR><BR> <BR>
<HR id=stopSpelling>
From: jay.krell@cornell.edu<BR>To: wagner@elegosoft.com<BR>Date: Mon, 12 Apr 2010 21:14:47 +0000<BR>CC: m3devel@elegosoft.com<BR>Subject: Re: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?<BR><BR>
<STYLE>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
I see part of the problem.<BR> - You do define the version earlier in the build, but not later. From reading the log.<BR> - I don't know why the grep doesn't work.<BR> <BR> <BR>Searching for '-DROOT'...<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(133):BUILDLOCAL="${CM3} -build -override -DROOT='${CM3ROOT}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(134):CLEANLOCAL="${CM3} -clean -override -DROOT='${CM3ROOT}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(135):BUILDGLOBAL="${CM3} -build -DROOT='${CM3ROOT}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(136):CLEANGLOBAL="${CM3} -clean -DROOT='${CM3ROOT}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(137):SHIP="${CM3} -ship -DROOT='${CM3ROOT}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(21):DEFS="-DROOT='${CM3ROOT}' -DCM3_VERSION_TEXT='${CM3VERSION}' -DCM3_VERSION_NUMBER='${CM3VERSIONNUM}' -DCM3_LAST_CHANGED='${CM3LASTCHANGED}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgmap.sh(424): echo " +++ cm3 -build -override -DTEST -DRUN -DROOT=$ROOT +++"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgmap.sh(429): tres=`cm3 -build -override -DTEST -DRUN -DROOT="${ROOT}" 2> stderr`<BR><BR> <BR>Maybe use ${DEFS} more?<BR>You could also hack cm3/src/m3makefile for the release. Copy the data into it.<BR>A better fix in head for the next one?<BR> <BR> <BR>Searching for 'DEFS'...<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(21):DEFS="-DROOT='${CM3ROOT}' -DCM3_VERSION_TEXT='${CM3VERSION}' -DCM3_VERSION_NUMBER='${CM3VERSIONNUM}' -DCM3_LAST_CHANGED='${CM3LASTCHANGED}'"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(22):BUILDLOCAL="${BUILDLOCAL:-${CM3} -build -override \$RARGS ${DEFS} ${BUILDARGS}}"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(23):CLEANLOCAL="${CLEANLOCAL:-${CM3} -clean -override \$RARGS ${DEFS} ${CLEANARGS}}"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(24):BUILDGLOBAL="${BUILDGLOBAL:-${CM3} -build ${DEFS} \$RARGS ${BUILDARGS}}"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(25):CLEANGLOBAL="${CLEANGLOBAL:-${CM3} -clean ${DEFS} \$RARGS ${CLEANARGS}}"<BR>C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(26):SHIP="${SHIP:-${CM3} -ship \$RARGS ${DEFS} ${SHIPARGS}}"<BR><BR> <BR>Is DEFS missing somewhere?<BR> <BR> <BR> - Jay<BR> <BR>
<HR id=ecxstopSpelling>
From: jay.krell@cornell.edu<BR>To: wagner@elegosoft.com<BR>Date: Mon, 12 Apr 2010 21:07:02 +0000<BR>CC: m3devel@elegosoft.com<BR>Subject: Re: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?<BR><BR>
<STYLE>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
I'm *guessing* some *sh problem.<BR>Want to try /usr/bin/bash?<BR> <BR> - Jay<BR><BR><BR> <BR>
<HR id=ecxecxstopSpelling>
From: jay.krell@cornell.edu<BR>To: wagner@elegosoft.com<BR>Date: Mon, 12 Apr 2010 20:59:34 +0000<BR>CC: m3devel@elegosoft.com<BR>Subject: Re: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?<BR><BR>
<STYLE>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
SOLgnu partial explanation:<BR> Building cm3 itself is going down the path that occurs when you don't -DCM3_VERSION_NUMBER -DCM3_VERSION_TEXT -DCM3_LAST_CHANGED.<BR> Not specifying them is supposed to work, but "you" are supposed to specify them really.<BR> Enough of a hint? (I don't have the full answer myself.)<BR> <BR> - Jay<BR><BR> <BR>> Date: Mon, 12 Apr 2010 17:05:48 +0200<BR>> From: wagner@elegosoft.com<BR>> To: jay.krell@cornell.edu<BR>> CC: m3devel@elegosoft.com<BR>> Subject: RE: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?<BR>> <BR>> Quoting Jay K <jay.krell@cornell.edu>:<BR>> <BR>> ><BR>> > Thanks. I see the NT386 packages, but not .msi.<BR>> <BR>> I'll check that later; the new index isn't in place, and perhaps<BR>> the update script is still buggy.<BR>> <BR>> Please have a look at the SOLgnu build though:<BR>> <BR>> <BR>> http://hudson.modula3.com:8080/view/makedist/job/cm3-makedist-SOLgnu/16/console<BR>> <BR>> This used to work. Anything you changed?<BR>> <BR>> Olaf<BR>> ><BR>> ><BR>> ><BR>> > - Jay<BR>> ><BR>> ><BR>> >> Date: Mon, 12 Apr 2010 13:13:11 +0200<BR>> >> From: wagner@elegosoft.com<BR>> >> To: m3devel@elegosoft.com<BR>> >> Subject: [M3devel] release 5.8 RC5 build in progress, was: Re: <BR>> >> release engineering: build release_CM3_5_8_RC5 now?<BR>> >><BR>> >> Quoting wagner@elegosoft.com:<BR>> >><BR>> >> > I'm currently tagging the release branch with release_CM3_5_8_RC5.<BR>> >> ><BR>> >> > Are there still any objections to use the current state of the branch?<BR>> >> ><BR>> >> > I'll soon try a sample build on birch.<BR>> >><BR>> >> As nobody has called `Stop', I've started to build the release packages<BR>> >> for RC5. Some can already be found on the download page currently<BR>> >> still reachable via the RC4 download (scroll down to the end).<BR>> >><BR>> >> http://www.modula3.com/cm3/releng/download.html<BR>> >><BR>> >> There have been 401 single changes since the last RC though :-/<BR>> >> See<BR>> >> http://hudson.modula3.com:8080/view/makedist/job/cm3-makedist-AMD64_LINUX/changes<BR>> >> for details. I don't know how to summarize that or even to motivate<BR>> >> this amound of changes that late in a release. Perhaps it's best to<BR>> >> just say nothing...<BR>> >><BR>> >> If you find any problem with RC5, please let me know as soon as possible.<BR>> >><BR>> >> Olaf<BR>> >> --<BR>> >> Olaf Wagner -- elego Software Solutions GmbH<BR>> >> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<BR>> >> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<BR>> >> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<BR>> >> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<BR>> >><BR>> ><BR>> <BR>> <BR>> <BR>> -- <BR>> Olaf Wagner -- elego Software Solutions GmbH<BR>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<BR>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<BR>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<BR>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<BR>> <BR> </body>
</html>