<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Sorry I do not. All I can do is scp the files to my home directory on birch and have "someone else" make them available otherwise.<BR>
I made them world readable. If you have access to birch, look in ~jkrell.<BR>
I'm not an ssh/scp expert, but this might work:<BR>
<BR>
scp <A href="mailto:yourname@m3.elegosoft.com:~jkrell/*.bz2">yourname@m3.elegosoft.com:~jkrell/*.bz2</A> . <BR>
<BR>
I don't now if ~ works here.<BR>
<BR>
I should have listed the file names, sorry. Later.<BR>
I think I deleted all the native Win32 files so that will net you three files all relevant.<BR>
Or if you can ls in the directory...the "min" one imho is the most interesting, you can build the others easily from it.<BR>
<BR>
Maybe try bootstrapping as kind of detailed below? :)<BR>
(That should be tested as well.)<BR>
<BR>
Maybe Trestle tonight, we'll see..<BR>
<BR>
- Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> CC: m3devel@elegosoft.com<BR>> From: darko@darko.org<BR>> To: jayk123@hotmail.com<BR>> Subject: Re: [M3devel] NT386GNU distribution available<BR>> Date: Mon, 21 Jan 2008 21:37:40 -0800<BR>> <BR>> Do you have a link for the distribution, or did I miss something?<BR>> <BR>> - Darko<BR>> <BR>> On 21/01/2008, at 8:41 AM, Jay wrote:<BR>> <BR>> > Here, in my user directory on birch, is the first CM3 NT386GNU <BR>> > release.<BR>> > It is MinGWin based FOR NOW.<BR>> > This needs to be changed SOON.<BR>> ><BR>> > Install MinGWin. (Search the web for it.)<BR>> > set PATH=c:\MinGW\bin;%PATH%<BR>> ><BR>> > (The default install location is c:\MinGW, not MinGWin.)<BR>> ><BR>> > The MinGWin that Qt gives you is too old, from around 2004.<BR>> > It doesn't support "response files" (aka long command lines).<BR>> ><BR>> > If you want to rebuild m3cg:<BR>> ><BR>> > Install MSys. It is at the same place as MinGWin.<BR>> > set PATH=c:\msys\1.0\bin;%PATH%<BR>> ><BR>> > else consider<BR>> ><BR>> > set OMIT_GCC=yes<BR>> ><BR>> > depending on if you run the various scripts.<BR>> ><BR>> > If you install to these exact paths, scripts\python\pylib.py<BR>> > will use them automatically.<BR>> ><BR>> > Optionally install Python. I recommend it.<BR>> ><BR>> > Extract one or more of the archives.<BR>> > They will extract to like:<BR>> ><BR>> > cm3-min-WIN32-NT386GNU-d5.5.1\bin\cm3.exe<BR>> ><BR>> > You can rename it cm3, or for purposes of backup/restore,<BR>> > xcopy /fivery \cm3-min-WIN32-NT386GNU-d5.5.1 \cm3<BR>> ><BR>> > (For extra good testing, first rmdir /q/s \cm3.)<BR>> ><BR>> > set PATH=c:\cm3\bin;%PATH%<BR>> ><BR>> > This is important, since various code will tend to assume NT386 <BR>> > unless overridden.<BR>> ><BR>> > set CM3_TARGET=NT386GNU<BR>> ><BR>> > Someone please weigh in on zip vs. tar.bz2 on the other Win32 <BR>> > platforms.<BR>> > For reference, MinGWin doesn't include tar/bzip2, MSys does, Cygwin<BR>> > has tons of optional stuff, they are in there, probably the base.<BR>> ><BR>> > And then go to scripts\python and run whatever:<BR>> > upgrade<BR>> > or make-dist<BR>> > or do-cm3-core<BR>> > or do-cm3-base<BR>> > but not currently do-cm3-std<BR>> ><BR>> > scripts\win\upgrade works too.<BR>> ><BR>> > Do remember to set CM3_TARGET=NT386GNU.<BR>> ><BR>> > You will probably at some point be prompted to set CM3_ROOT to the <BR>> > root of the source<BR>> > tree as well. If you run "scripts", it will be set for you.<BR>> > If you cd around and run cm3, it won't.<BR>> ><BR>> > \cm3\bin\cm3.cfg delegates out to the source tree.<BR>> > Except the one in the distributions do not.<BR>> > But if you run upgrade, you'll have such a thing.<BR>> ><BR>> > If you want to rebuild cm3cg from source:<BR>> > cd m3-sys\m3cc\gcc\gcc\m3cg<BR>> > cvs update -j 1.46 -j 1.45 parse.c<BR>> ><BR>> > or thereabouts to get back enough of a __stdcall fix to build a lot.<BR>> ><BR>> > If you want to bootstrap without a previous NT386GNU distribution <BR>> > but with<BR>> > a previous NT386 build, try like this:<BR>> ><BR>> > Get a working NT386 system.<BR>> > Get current source (except parse.c).<BR>> > If your system is not current,<BR>> > scripts\python\upgrade<BR>> > This will work as far back as cm3-min-WIN32-NT386-5.1.3.<BR>> > scripts\python\bootntgnu<BR>> > which is really just roughly:<BR>> > do-pkg realclean m3core libm3 m3cc<BR>> > do-pkg buildship m3core libm3 m3cc<BR>> > set CM3_TARGET=NT386GNU<BR>> > Now you have the equivalent of the minimum distribution and <BR>> > can build whatever.<BR>> > do-pkg ....<BR>> ><BR>> > If you want to rollback a bit but not completely, scripts\win <BR>> > \pkggnu_clean.cmd is<BR>> > very simple and just deletes all the NT386GNU directories under <BR>> > $INSTALLROOT\pkg.<BR>> ><BR>> > There are "min", "core", and "base" distributions.<BR>> > Kind of subtle names, eh?<BR>> > "min" is sufficient.<BR>> > The binaries are all not "strippped".<BR>> ><BR>> > Last minute errata:<BR>> > There is bin\cm3.cfg and bin\NT386GNU. They are identical.<BR>> > The intent was only to have cm3.cfg there.<BR>> ><BR>> > The system builds itself, so that's pretty good.<BR>> ><BR>> > I forgot to include m3gdb, but it should probably be in a separate <BR>> > "GNU" archive?<BR>> ><BR>> > Someone move the files to a web download place?<BR>> > (and you can move, not copy, I can easily recreate the files)<BR>> ><BR>> > - Jay<BR>> ><BR>> > Shed those extra pounds with MSN and The Biggest Loser! Learn more.<BR>> <BR><BR><br /><hr />Shed those extra pounds with MSN and The Biggest Loser! <a href='http://biggestloser.msn.com/' target='_new'>Learn more.</a></body>
</html>