1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 <meta name="generator" content="Movable Type 5.2.3" />
8 <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
9 <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
10 <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
12 <title>Status for Andrew DeFaria: December 5, 2004 - December 11, 2004 Archives</title>
14 <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
15 <link rel="prev" href="http://defaria.com/blogs/Status/archives/week_2004_09_19.html" title="September 19, 2004 - September 25, 2004" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2004_12_12.html" title="December 12, 2004 - December 18, 2004" />
18 <body class="layout-one-column">
20 <div id="container-inner" class="pkg">
23 <div id="banner-inner" class="pkg">
24 <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
25 <h2 id="banner-description">Searchable status reports and work log</h2>
30 <div id="pagebody-inner" class="pkg">
32 <div id="alpha-inner" class="pkg">
34 <p class="content-nav">
35 <a href="http://defaria.com/blogs/Status/archives/week_2004_09_19.html">« September 19, 2004 - September 25, 2004</a> |
36 <a href="http://defaria.com/blogs/Status/">Main</a>
37 | <a href="http://defaria.com/blogs/Status/archives/week_2004_12_12.html">December 12, 2004 - December 18, 2004 »</a>
43 <h2 class="date-header">December 10, 2004</h2>
45 <div class="entry" id="entry-256">
46 <h3 class="entry-header">Building 5.0.0 ppc cross toolchain</h3>
47 <div class="entry-content">
48 <div class="entry-body">
51 <li>Built 5.0.0 ppc cross toolchain - looking for ppc to build native</li>
53 <li>Rebuilding 5.0.0 ppc using previous toolchain (having problems)</li>
57 <p class="entry-footer">
58 <span class="post-footers">Posted by at 3:06 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000256.html">Permalink</a>
68 <h2 class="date-header">December 9, 2004</h2>
70 <div class="entry" id="entry-255">
71 <h3 class="entry-header">Building 5.0.0 for ppc</h3>
72 <div class="entry-content">
73 <div class="entry-body">
76 <li>Built 5.0.0 for ppc</li>
82 <p>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.</p>
84 <p>Building for ppc takes a long time as our ppc machines are slow and there's a lot more to build for ppc.</p>
86 <p class="entry-footer">
87 <span class="post-footers">Posted by at 3:04 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000255.html">Permalink</a>
97 <h2 class="date-header">December 8, 2004</h2>
99 <div class="entry" id="entry-254">
100 <h3 class="entry-header">Booting 5.0.0 LynxOS</h3>
101 <div class="entry-content">
102 <div class="entry-body">
105 <li>Used loadit.exp to run ATS of for this new 5.0.0 LynxOS
109 <p>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.</p>
111 <p><b>Note:</b> loadit.exp <b>requires</b> 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!</p>
113 <p class="entry-footer">
114 <span class="post-footers">Posted by at 11:37 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000254.html">Permalink</a>
124 <h2 class="date-header">December 7, 2004</h2>
126 <div class="entry" id="entry-253">
127 <h3 class="entry-header">Building 5.0.0 TOT toolchain</h3>
128 <div class="entry-content">
129 <div class="entry-body">
132 <li>Built 3.2.2 toolchain natively on Lynxos 5.0.0</li>
136 <p>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.<p>
138 <p>Build failed again, this time <i>Memory Exhausted</i>. I had to do <tt>ulimit -s -d 1000000</tt> and restart build</p>
140 <p>Build finally succeeded. Did make package then copied to t3 area (to be precise <tt>t3:/export/dev_archive/lynxos/tools-5.0.0/3.2.2-120604</tt>). Only needed to copy over the <tt>toolchain-i386-lynx-lynxos-i386.tar.gz</tt> as this package is the 5.0.0 toolchain built natively</p>
142 <p>Created a new build area on dopey @ <tt>/export/build1/LYNXOS_500/build/lynxos/120604-C</tt>. Needed to copy over int_tools and modify <tt>int_tools/__profile.exp</tt> to:
146 <li>Change <tt>DIR_PATH(archive)</tt> back to dopey (it was at t3 for 120604-B) </li>
148 <li>Change <tt>int_tools/EXP_LIB/steps.exp</tt> to use gnuaout instead of gnu in the name of the package. There is a little debate of which way this should go</li>
152 <p><b>Note:</b> 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 <i>int_tools</i> 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 <i>int_tools</i> 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.</p>
154 <p class="entry-footer">
155 <span class="post-footers">Posted by at 6:54 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000253.html">Permalink</a>
165 <h2 class="date-header">December 6, 2004</h2>
167 <div class="entry" id="entry-252">
168 <h3 class="entry-header">Building LynxOS with gcc 3.2.2</h3>
169 <div class="entry-content">
170 <div class="entry-body">
173 <p><li>Build 3.2.2 toolchain successfully</li></p>
178 <p>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.</p>
180 <p class="entry-footer">
181 <span class="post-footers">Posted by at 5:01 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000252.html">Permalink</a>