[M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?

Jay K jay.krell at cornell.edu
Mon Apr 12 23:24:03 CEST 2010


A good option is to export these three variables:

 

  CM3VERSIONNUM  
  CM3VERSION
  CM3LASTCHANGED


and/or use the -D switches.

Otherwise m3-sys/cm3/m3makefile goes down a gnarly path (that I put in) of trying to read scripts/version.

  Which usually works, but could be too sensitive to /bin/sh behavior...often bites us you know.

 

 - Jay

 


From: jay.krell at cornell.edu
To: wagner at elegosoft.com
Date: Mon, 12 Apr 2010 21:14:47 +0000
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?



I see part of the problem.
 - You do define the version earlier in the build, but not later. From reading the log.
 - I don't know why the grep doesn't work.
 
 
Searching for '-DROOT'...
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(133):BUILDLOCAL="${CM3} -build -override -DROOT='${CM3ROOT}'"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(134):CLEANLOCAL="${CM3} -clean -override -DROOT='${CM3ROOT}'"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(135):BUILDGLOBAL="${CM3} -build  -DROOT='${CM3ROOT}'"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(136):CLEANGLOBAL="${CM3} -clean -DROOT='${CM3ROOT}'"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\make-bin-dist-min.sh(137):SHIP="${CM3} -ship -DROOT='${CM3ROOT}'"
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}'"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgmap.sh(424):            echo " +++ cm3 -build -override -DTEST -DRUN -DROOT=$ROOT +++"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgmap.sh(429):            tres=`cm3 -build -override -DTEST -DRUN -DROOT="${ROOT}" 2> stderr`

 
Maybe use ${DEFS} more?
You could also hack cm3/src/m3makefile for the release. Copy the data into it.
A better fix in head for the next one?
 
 
Searching for 'DEFS'...
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}'"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(22):BUILDLOCAL="${BUILDLOCAL:-${CM3} -build -override \$RARGS ${DEFS} ${BUILDARGS}}"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(23):CLEANLOCAL="${CLEANLOCAL:-${CM3} -clean -override \$RARGS ${DEFS} ${CLEANARGS}}"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(24):BUILDGLOBAL="${BUILDGLOBAL:-${CM3} -build ${DEFS} \$RARGS ${BUILDARGS}}"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(25):CLEANGLOBAL="${CLEANGLOBAL:-${CM3} -clean ${DEFS} \$RARGS ${CLEANARGS}}"
C:\DEV2\CM3.RELEASE_BRANCH_CM3_5_8\SCRIPTS\pkgcmds.sh(26):SHIP="${SHIP:-${CM3} -ship \$RARGS ${DEFS} ${SHIPARGS}}"

 
Is DEFS missing somewhere?
 
 
 - Jay
 


From: jay.krell at cornell.edu
To: wagner at elegosoft.com
Date: Mon, 12 Apr 2010 21:07:02 +0000
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?



I'm *guessing* some *sh problem.
Want to try /usr/bin/bash?
 
 - Jay


 


From: jay.krell at cornell.edu
To: wagner at elegosoft.com
Date: Mon, 12 Apr 2010 20:59:34 +0000
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?



SOLgnu partial explanation:
  Building cm3 itself is going down the path that occurs when you don't -DCM3_VERSION_NUMBER -DCM3_VERSION_TEXT -DCM3_LAST_CHANGED.
  Not specifying them is supposed to work, but "you" are supposed to specify them really.
  Enough of a hint? (I don't have the full answer myself.)
 
 - Jay

 
> Date: Mon, 12 Apr 2010 17:05:48 +0200
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: RE: [M3devel] release 5.8 RC5 build in progress, was: Re: release engineering: build release_CM3_5_8_RC5 now?
> 
> Quoting Jay K <jay.krell at cornell.edu>:
> 
> >
> > Thanks. I see the NT386 packages, but not .msi.
> 
> I'll check that later; the new index isn't in place, and perhaps
> the update script is still buggy.
> 
> Please have a look at the SOLgnu build though:
> 
> 
> http://hudson.modula3.com:8080/view/makedist/job/cm3-makedist-SOLgnu/16/console
> 
> This used to work. Anything you changed?
> 
> Olaf
> >
> >
> >
> > - Jay
> >
> >
> >> Date: Mon, 12 Apr 2010 13:13:11 +0200
> >> From: wagner at elegosoft.com
> >> To: m3devel at elegosoft.com
> >> Subject: [M3devel] release 5.8 RC5 build in progress, was: Re: 
> >> release engineering: build release_CM3_5_8_RC5 now?
> >>
> >> Quoting wagner at elegosoft.com:
> >>
> >> > I'm currently tagging the release branch with release_CM3_5_8_RC5.
> >> >
> >> > Are there still any objections to use the current state of the branch?
> >> >
> >> > I'll soon try a sample build on birch.
> >>
> >> As nobody has called `Stop', I've started to build the release packages
> >> for RC5. Some can already be found on the download page currently
> >> still reachable via the RC4 download (scroll down to the end).
> >>
> >> http://www.modula3.com/cm3/releng/download.html
> >>
> >> There have been 401 single changes since the last RC though :-/
> >> See
> >> http://hudson.modula3.com:8080/view/makedist/job/cm3-makedist-AMD64_LINUX/changes
> >> for details. I don't know how to summarize that or even to motivate
> >> this amound of changes that late in a release. Perhaps it's best to
> >> just say nothing...
> >>
> >> If you find any problem with RC5, please let me know as soon as possible.
> >>
> >> Olaf
> >> --
> >> Olaf Wagner -- elego Software Solutions GmbH
> >> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> >> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> >> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> >> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
> >>
> >
> 
> 
> 
> -- 
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100412/f147b8e5/attachment-0002.html>


More information about the M3devel mailing list