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 12, 2004 - December 18, 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_12_05.html" title="December 5, 2004 - December 11, 2004" />
16 <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2004_12_19.html" title="December 19, 2004 - December 25, 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_12_05.html">« December 5, 2004 - December 11, 2004</a> |
36 <a href="http://defaria.com/blogs/Status/">Main</a>
37 | <a href="http://defaria.com/blogs/Status/archives/week_2004_12_19.html">December 19, 2004 - December 25, 2004 »</a>
43 <h2 class="date-header">December 17, 2004</h2>
45 <div class="entry" id="entry-260">
46 <h3 class="entry-header">LOS178 Build/5.0.0 native toolchain build</h3>
47 <div class="entry-content">
48 <div class="entry-body">
51 <li>LOS178 build after copyright fix builds with 12 errors. Test build of LOS178 without copyright fix also builds with 12 errors!</li>
53 <li>Building of 5.0.0 toolchain natively is failing</li>
57 <h3>LOS178 copyright fix</h3>
59 <p>The Perl script to fix the copyrights in LOS178 sources needs detect if there was a prior copyright block and replace it if necessary. Finding old copyright blocks is hueristic in nature and thus fallable. The problem is there are no sentenals clearly marking our copyright. The best the script can do is attempt to find a comment block that starts and ends with a particular comment line based on the "/" and a number of "*"'s for the start and a number of "*"'s and a "/" for the end. Problem is we do not know if what's inbetween is really our copyright. The hueristic can be tuned finer with some difficulty but currently it does not.</p>
61 <p>The real difficulty is that there is no real standard in our copyright blocks thus it is hard to get this right</p>
63 <p>As it stands the script occasionally misinterprets a comment block, sometimes just the ending comment block, and alters the file in such a way that it introduces compile errors.</p>
65 <p>There were a number of files that this occurred in and they were hand edited</p>
67 <h3>5.0.0 Native Toolchain Build</h3>
69 <p>In picking up ECR 23084 I was able to build the toolchain for both cross x86 and ppc. In building the native toolchain there is an error:</p>
72 Configuring texinfo...
73 configure: error: invalid package name: gcc-version-trigger
74 Configure in /mnt/toolchain/build-i386/texinfo failed, exiting.
75 make: *** [stamp-configure-i386] Error 1
78 <p>Thu says that I didn't run fixup.sh but I did. The toolchain does not package up fixup.sh so I grabbed one from somewhere. Thu suggests that we file an ECR for this and fix the Makefile.</p>
80 <p class="entry-footer">
81 <span class="post-footers">Posted by at 10:38 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000260.html">Permalink</a>
91 <h2 class="date-header">December 16, 2004</h2>
93 <div class="entry" id="entry-259">
94 <h3 class="entry-header">LOS178 & ECR 23084</h3>
95 <div class="entry-content">
96 <div class="entry-body">
99 <li>Wrote a Perl script to fix up copyrights on LynxOS (178). Working on running that and getting the build to work</li>
101 <li>Pulled ECR 23084 and built toolchain for x86 & ppc. Need to build native</li>
105 <p class="entry-footer">
106 <span class="post-footers">Posted by at 9:24 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000259.html">Permalink</a>
116 <h2 class="date-header">December 14, 2004</h2>
118 <div class="entry" id="entry-258">
119 <h3 class="entry-header">ECRs 23079 & 23080</h3>
120 <div class="entry-content">
121 <div class="entry-body">
124 <li>Submitted ECR: 23079: PPC: target elf32-powerpc-lynx not found</li>
126 <li>Submitted ECR: 23080: OUTPUT_FORMAT directive should be adjusted to elf32-powerpc-lynx</li>
130 <p>Thu determined that we have a toolchain problem here so she had me submit ECR 23079. Adam debugged the problem which produced 23080</p>
132 <p class="entry-footer">
133 <span class="post-footers">Posted by at 4:55 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000258.html">Permalink</a>
143 <h2 class="date-header">December 13, 2004</h2>
145 <div class="entry" id="entry-257">
146 <h3 class="entry-header">Rebuilding PPC</h3>
147 <div class="entry-content">
148 <div class="entry-body">
151 <li>Rebuilding for the PPC. I messed up a step or two</li>
155 <h2>Building cross lynxos for PPC</h2>
159 <li>Cleaned up by removing the ppc directories (i.e. starting from scratch WRT the ppc)</li>
161 <li>Linked /usr/lynx/5.0.0 -> /export/build1/LYNXOS_500/build/lynxos/120604-A</li>
163 <li>In /export/build1/LYNXOS_500/build/lynxos/120604-A/int_tools modified START to change steps_ppc to just 1 and 2. We're gonna take this slowly.</li>
165 <li>Made sure that __profile.exp points to 120604-A. It still does, from before. There are a lot of settings in here that sometimes need to change depending on the situation. For example, right now the TOP_OF_TRUNK variable is set to no but it is usually set to yes.</li>
167 <li>Execute START and then tail -f LOGS/ppc.log.</li>
169 <li>Checked out with "check ppc". Seems OK.</li>
171 <li>Changed START to do steps 3 and 4. I think I could have done 1, 2, 3 and 4 together but Thu only wrote down 1 and 2</li>
173 <li>Checked again with check ppc. Still seems fine</li>
175 <li>Changed START to do steps 5en 5el 7 9 14 15 16 (17 doesn't work yet so why do it?) <font color="red"><b>Failure:</b></font> got:<br>
178 Failure reason : Compiler does not exist: /export/dev_archive/lynxos/tools-5.0.0/3.2.2-072304/toolchain-powerpc-lynx-lynxos-ppc.tar.gz
181 Ah ha! See this is one of those things that just confuses me. Contained in __profile.exp there's:
185 #set DIR_PATH(compilers) "/usr/lynx/t3/dev_archive/lynxos/tools-5.0.0/3.2.2-072304"
186 set DIR_PATH(compilers) "/export/dev_archive/lynxos/tools-5.0.0/3.2.2-072304"
189 need to uncomment the first line and comment out the second line.</li>
191 <li>After making the above change I reran START. Errors in makeall.log</li>
195 <h2>Build ppc toolchain</h2>
197 <p>Thu said that the error sin makeall.log were acceptable. Continuing on to build the ppc toolchain...</p>
201 <li>cd /usr/lynx/5.0.0/ppc (note that /usr/lynx/5.0.0 still points to 120604-A)</li>
203 <li>Ran . SETUP.bash setting ENV_PREFIX to cwd, target = ppc. which gcc yeilds /usr/lynx/5.0.0/ppc/cdk/linux-elf-ppc/bin/gcc</li>
205 <li>Toolchain is in /export/build1/LYNXOS_500/build/toolchain/3.2.2/120804 so cd'ed there</li>
207 <li>make install > install-ppc.log 2>&1 &</li>
209 <li>Toolchain seemed to build OK this time. Archived toolchain by doing make package then moving toolchain-i686-pc-linux-gnu-powerpc.tar.gz to /usr/lynx/t3/dev_archive/lynxos/tools-5.0.0/3.2.2-120604. This is a little tricky because this path is a link to a mount on t3 and as such is considered a read only file system. The following worked for me, in /export/build1/LYNXOS_500/build/toolchain/3.2.2/120804:</li>
212 $ rcp toolchain-i686-pc-linux-gnu-powerpc.tar.gz int@t3:/export/dev_archive/lynxos/tools-5.0.0/3.2.2-120604
217 <h2>Building cross lynxos for PPC (again)</h2>
221 <li>Linked /usr/lynx/5.0.0 -> /export/build1/LYNXOS_500/build/lynxos/120604-B</li>
223 <li>In /export/build1/LYNXOS_500/build/lynxos/120604-B/int_tools modified START to change steps_ppc to for 1, 2, 3 and 4.</li>
225 <li>Execute START and then tail -f LOGS/ppc.log. Steps 1-4 seemed to have worked OK</li>
227 <li>Looked at __profile.exp and found
229 <tt><pre>set DIR_PATH(compilers) "/usr/lynx/t3/dev_archive/lynxos/tools-5.0.0/3.2.2-120604"
232 The compiler exists there (because of the archiving step above). Note there was no t3 style reference here.</li>
234 <li>Ran START again and monitored logs... Errors stating "gcc: installation problem, cannot exec `cc1': No such file or directory"</li>
239 <p class="entry-footer">
240 <span class="post-footers">Posted by at 2:40 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000257.html">Permalink</a>