[M3devel] building CM3 on a Raspberry Pi?

[mika at async.caltech.edu]

Jay writes:
...
>Cm3.cfg: yes it might do that. I can see about using a separate file but no p=
>romises there. A flaw perhaps in some of my earlier thinking was over eagern=
>ess in when the config files get updated. The older config files were in gen=
>eral very flawed IMHO. But maybe good to leave them alone in early bootstrap=
>, if they worked. But I really had a lot of problems with them. The current o=
>nes don't require cminstall, have less version/target-specific code, have fa=
>r less duplication, and are meant to work with older cm3 (albeit maybe give u=
>p on dynamic linking with older versions).
...

My point here was just this... I have a system with a working compiler.  Everything
is set up carefully to work with all the various packages and things and strange
flags I might need to get everything working on my very very special machine.  It's
all in cm3.cfg, no?  Now, I want to build a cross compiler, just so I can bootstrap
an installation on another system.  And the first thing that happens is I lose my
own very carefully crafted installation configuration?  Is that really right?  Or
am I misunderstanding something about the process?

More updates are that I got the same error about the tree file on Linux (quite recent
install), so it must be an issue with the gcc.  I'll try your suggestions..

     Mika