Building 5.0.0 ppc cross toolchain
- Built 5.0.0 ppc cross toolchain - looking for ppc to build native
- Rebuilding 5.0.0 ppc using previous toolchain (having problems)
« September 19, 2004 - September 25, 2004 | Main | December 12, 2004 - December 18, 2004 »
I was under a mistaken assumption that I needed to have a PPC machine in order to do this and was waiting for one. Thu informed me that I could build 5.0.0 for cross and even rebuild the toolchain cross - that I wouldn't need a ppc machine until I needed to build a native gcc.
Building for ppc takes a long time as our ppc machines are slow and there's a lot more to build for ppc.
Failed to get loadit.exp to work. Seems that it is oriented to getting the images off of t3. But I didn't put this new images on T3 yet. Seems there's some rync process that Thu flew by me and I missed.
Note: loadit.exp requires a working network connection to the System Under Test! When last we left t-k1g-1 it was booted to lynxos with non-working networking. loadit.exp sits and waits at an rcp command and the SUT never responds!
Came in to find that the native build of the 5.0 toolchain went nowhere. Seems, as I expected, that I need to unpack 18010.x11r6.tar.gz and 18011.pd.tar.gz too. Unpacked that and restarted build.
Build failed again, this time Memory Exhausted. I had to do ulimit -s -d 1000000 and restart build
Build finally succeeded. Did make package then copied to t3 area (to be precise t3:/export/dev_archive/lynxos/tools-5.0.0/3.2.2-120604). Only needed to copy over the toolchain-i386-lynx-lynxos-i386.tar.gz as this package is the 5.0.0 toolchain built natively
Created a new build area on dopey @ /export/build1/LYNXOS_500/build/lynxos/120604-C. Needed to copy over int_tools and modify int_tools/__profile.exp to:
Note: I find all of these different machines with different long pathnames confusing. For example, I would think using the principal of separation of code and data that the int_tools code should be globally accessible and that one should not be modifying variable contents before running scripts. That's data and should either have to be supplied or kept in a data file perhaps separate for each build run. IOW int_tools should be globally visable (perhaps in one's PATH) and execuable as code and not modified per run. Also, as such it should in CVS and perhaps grabbed from CVS with an official TAG.
Managed to build the toolchain (gcc 3.2.2) successfully. We had to first build LynxOS then build the compiler then build LynxOS again. Confusing indeed. Lot's of paths and scripts. I'm still not totally comfortable with the environment, how to build, native vs. cross, toolchain vs. LynxOS, CVS top of trunk, etc.