- Built 3.2.2 toolchain natively on Lynxos 5.0.0
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:
- Change DIR_PATH(archive) back to dopey (it was at t3 for 120604-B)
- Change int_tools/EXP_LIB/steps.exp to use gnuaout instead of gnu in the name of the package. There is a little debate of which way this should go
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.