add root\bin to %PATH% in the .msi installer
Back patch from newer bfd/binutils, to handle new elf section type
".gnu.hash", SHT_GNU_HASH, with code 6ffffff6.  Apparently, (m3)gdb
doesn't do anything with this, but must be able to recognize its
header, size, etc. when reading elf binaries.  This section type does
not appear to occur in Modula-3 code compiled on LINUXLIBC6 platforms,
but it does on AMD64_LINUX.

Note: m3gdb on AMD64_LINUX is showing other problems with handling
64-bit values.
Expand recognition of 64-bit targets to all those found
in m3middle/src/Target.m3 (and not commented out).
fixup package sets and platform filtering of packages


 fix_nl is a simple portable text file utility to convert newlines
  It is less needed on Posix platforms, but it builds and runs fine.
  On the other hand, it isn't important, relegate it to tool.


 import-libs does its own platform filtering,
 so remove the filtering here
  It is kind of important when it is used, and kind of unimportant.
  Generally most Win32 toolsets supercede it, with the exception that
  the older CM3 toolsets contain invalid versions of it which
  it replaces and some minimal (Express) toolsets are only a subset of it.
   While it is an interesting example of several programming techniques,
   it'll probably be removed in the next release.
   (Deleting the invalid files suffices as long as a decent toolset is
in use.)


 mklib is only used when targeting NT386 and such, but is buildable
  and runnable on all hosts, so remove filtering here
  (on the other hand, cross bootstrapping doesn't use it currently,
  probably never will, since the goal is merely a standalone cm3 and
  no libs, so its importance is overstated;
  cross building if it evolves far could easily use something from
  GNU binutils instead, e.g. ld or dlltool;
  that is, it is important min/core/base for NT386 hosts/targets,
  but could be relegated to "tool" otherwise,
  but package sets aren't changable per platform, probably ok/good)


 libdump isn't used, relegate it to "tool"
   It was possibly used in the past, like when custom import libs
   were built
   (The above-mentioned invalid ones; import-libs just builds
   normal ones using the native linker.)


 m3staloneback is a command line driver for a subset of cm3, in normal
  situations you just use cm3, relegate it to "tool"


 m3cggen just outputs a generated .h file that is checked in and only
  changed when new IL forms are added, relegate it to "tool"
  (something like
  not-useful-to-most-people-but-it-is-somewhere-so-we-build-it would be
  good, that would be m3cggen, m3cgcat; and
  not-useful-to-anyone-at-all-likewise would
  be fix_nl (I use dos2unix) and libdump (redundant with link -dump))


 m3cgcat is largely redundant with cm3cg -y, but more informative, but
  only useful to people changing/debugging cm3cg (highly useful, to
  very few people), so relegate it to "tool"


 m3objfile is built for all platforms
 It used to be, I recall, that cm3 could either run cm3cg OR use the
  integrated backend but long ago I changed it to to either
  determined at runtime for some cross build functionality.
more package set cleanup: remove m3staloneback, put mklib in for all platforms
more package set cleanup: m3back, m3staloneback for all platforms
remove readonly on m3back_flags, SYSTEM_CC, SYSTEM_LD
 so that leaf m3makefiles can change them for aspects
 that aren't abstracted, though portability can
 be difficult
 (SYSTEM_ASM, SYSTEM_AR, SYSTEM_LIBTOOL less well motivated..leave them
alone)
 This might also reduce pressure on the desire to edit these files.
 (as would some if exist include sprinkling)

This will also let us do stuff like:
 SYSTEM_CC = something
 if equal(WORD, "64BITS")
   SYSTEM_CC = SYSTEM_CC & " -m64"
 else
   SYSTEM_CC = SYSTEM_CC & " -m32"
 end

 perl -pi.bak -e "s/readonly (m3back_flags|(SYSTEM_(CC|LD)))/\1/g" *
 cvs -z3 diff -u > 1.txt
 cvs -z3 commit `grep RCS 1.txt | perl -pi.bak -e "s/.+\///; s/,v//"`
  (since dumb cvs -z3 commit will include unchanged files)
try make it not executable
removing executable permission
working on removing executable permission
fixing executable permissions, no actual change
fixing executable permission, no diff
fixing executable permissions, no diff (should just keep all output out of the source tree, then don't need .cvsignore)
working on removing executable permission
working on removing executable permission
fixing executable permissions, no change
no change, just removing executable permission
just removing executable permissionse
fixing executable permissions
These are obsolete, they wouldn't work any longer and boto1.py works for many/all platforms.