<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><div style="text-align: left;">Starting with an older release on PPC_DARWIN and running upgrade.sh, I keep getting:<br><br></div>=== package /dev2/cm3/m3-sys/m3middle ===<br> +++ cm3 -build -DROOT='/dev2/cm3' -DCM3_VERSION_TEXT='d5.5.1' -DCM3_VERSION_NUMBER='050501' -DCM3_LAST_CHANGED='2007-12-30' && cm3 -ship -DROOT='/dev2/cm3' -DCM3_VERSION_TEXT='d5.5.1' -DCM3_VERSION_NUMBER='050501' -DCM3_LAST_CHANGED='2007-12-30' +++<br>--- building in PPC_DARWIN ---<br><br>ignoring ../src/m3overrides<br><br>stale imports -> compiling CoffTime.m3<br>stale imports -> compiling M3Process.i3<br>stale imports -> compiling M3Process.m3<br>stale imports -> compiling TFloat.m3<br><br>Fatal Error: bad version stamps: TFloat.m3<br><br>version stamp mismatch: TargetMap.Float_types<br> <31f4d45a27120488> => TFloat.m3<br> <663449bb704e9c85> => TargetMap.i3 <br> *** execution of failed ***<br><br><br>I assume this will be fixed by:<br><br>ijayk:/dev2/cm3/scripts jay$ cvs diff upgrade.sh<br>Index: upgrade.sh<br>===================================================================<br>RCS file: /usr/cvs/cm3/scripts/upgrade.sh,v<br>retrieving revision 1.4<br>diff -r1.4 upgrade.sh<br>52a53,55<br>> echo "$ROOT/scripts/do-pkg.sh" "$@" "realclean ${P}"<br>> "$ROOT/scripts/do-pkg.sh" "$@" "realclean" ${P} || exit 1<br>> <br>58a62,64<br>> echo "$ROOT/scripts/do-cm3-core.sh" "$@" "realclean"<br>> "$ROOT/scripts/do-cm3-core.sh" "$@" "realclean" || exit 1<br>> <br><br>Will that really harm/slow anyone's workflow?<br><br>In fact, notice how the older upgrade, while broken for other reasons, did this<br>dance with upgrading and restoring the pkg store.<br>win\upgrade.cmd still does.<br>Something to consider..<br>(And I realize that backup/restore of install/pkg is different than realclean of root/*, so maybe<br>that diff is not the fix.)<br><br>Though it is a problem to manage the versions, in doing the backup/restore.<br><br>Perhaps this all falls under the heading of -- not worth automating, people know what they are doing, else they can pickup a current binary distribution??<br><br>I'll get something working locally no doubt, I don't need any further help. :)<br>(Though past help has helped shed light here, the local/global/ship thing is still just a tad vague to me and I'm just slightly unconvinced it has to be this way, but probably it does, what with necessary circularities between compiler and runtime, building with an older compiler and all that...)<br><br> - Jay<br><br /><hr />Share life as it happens with the new Windows Live. <a href='http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008' target='_new'>Start sharing!</a></body>
</html>