<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Randy, ROOT not being defined is a function of your config files.<BR>
Look at mine. Mine are willing to ferry it from an environment variable.<BR>
The various scripts figure it out and set it on the command line.<BR>
e.g. sysinfo.sh<BR>
<BR>
Granted..I don't think ROOT is supposed to be required.<BR>
ROOT is the root of the source tree, as you correctly?successfully worked around.<BR>
You are supposed to be able to use the compiler without a source tree.<BR>
But you can't, um, build the source tree without a source tree.<BR>
<BR>
I am very tempted to have cm3.exe set ROOT itself,<BR>
but it is a bit inappropriate actually.<BR>
<BR>
PERHAPS if it was renamed CM3_ROOT...<BR>
<BR>
Olaf isn't saying "just use a current release", he is<BR>
saying "start with a current release" and then try to build locally.<BR>
<BR>
You cannot necessarily bootstrap from arbitrarily old releases.<BR>
But you should definitely be able to bootstrap from current snapshots.<BR>
<BR>
It does work.<BR>
<BR>
Whenever you get into a "bad state" -- after any failed run,<BR>
I encourage you to blow away the entire cm3 install and "start over".<BR>
<BR>
Several "partial builds" will leave you with a "mixed state".<BR>
<BR>
Some of the scripts do or used to "backup" the pkg store,<BR>
but I don't think it was worth the effort...the effort I put<BR>
in to clone the .sh in .cmd. I think I punted doing that in the *.py,<BR>
and I don't miss it.<BR>
<BR>
I also recommend trying the *.py files.<BR>
<BR>
> that always gets the undefined ROOT failure, even trying to compile<BR>> a trivial program.<BR><BR>
Hm. Could be your config file wants it?<BR>
Could be my config files wants it?<BR>
I guess the usual refrain -- send us your config file(s).<BR>
I can dig more later..maybe days..busy with other stuff..<BR>
<BR>
<BR>
- Jay<BR><BR>> Date: Thu, 13 Nov 2008 09:45:34 -0600<BR>> From: rodney<BR>> To: m3devel<BR>> Subject: Re: [M3devel] Still can't bootstrap cm3<BR>> <BR>> Olaf wrote:<BR>> > <BR>> > it's not easy to understand what has gone wrong at this point.<BR>> > Usually, if you have a working system, cm3/scripts/upgrade.sh<BR>> > should be able to bootstrap to a new set of sources. This is tested<BR>> > every day in the tinderbox release tests, too. As the last builds seem<BR>> > to have succeeded, I don't think there is a real problem in our<BR>> > code base currently. You may want to have a look at test_build_current<BR>> > in cm3/scripts/regression/defs.sh to see what's done in the regression<BR>> > builds.<BR>> > <BR>> > I'd suggest you either start again from the last release or<BR>> > one of the latest snapshots available from the build machine.<BR>> <BR>> Yes, that's what I always end up doing. But it would be nice to be<BR>> able someday to get my local compiler to rebuild itself :-(.<BR>> <BR>> But even that is not working for me. Reinstalling a snapshot from<BR>> 2008-6-6 and a fresh cvs checkout, upgrade.sh gives the missing<BR>> .M3EXPORTS failure, and do-cm3-core.sh (after realclean) gets bad<BR>> version stamps on Compiler.Platform and Compiler.ThisPlatform,<BR>> while compiling SocketPosix.m3.<BR>> <BR>> Going to the most recent (at the time) snapshot of 2008-11-12,<BR>> do-cm3-core.sh will run without failures, but leaves a compiler<BR>> that always gets the undefined ROOT failure, even trying to compile<BR>> a trivial program.<BR>> <BR>> > I assume you are not building a cross compiler, but just trying<BR>> > to perform an upgrade.<BR>> <BR>> That's right. The only reason I messed with the cross scripts was that<BR>> I hoped they might take care of the necessary bootstrapping in a way<BR>> the would work.<BR>> <BR>> > <BR>> > Daily snapshots are available from<BR>> > http://www.opencm3.net/snaps/snapshot-index.html<BR>> > <BR>> > I hope this helps,<BR>> > <BR>> > Olaf<BR>> > <BR>> ><BR><BR></body>
</html>