defaria.com/blogs/Status/archives/week_2005_01_09.html

   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">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   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"$>" />
  11
  12    <title>Status for Andrew DeFaria: January  9, 2005 - January 15, 2005 Archives</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/week_2005_01_02.html" title="January  2, 2005 - January  8, 2005" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2005_01_16.html" title="January 16, 2005 - January 22, 2005" />
  17 </head>
  18 <body class="layout-one-column">
  19    <div id="container">
  20       <div id="container-inner" class="pkg">
  21
  22          <div id="banner">
  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>
  26             </div>
  27          </div>
  28
  29          <div id="pagebody">
  30             <div id="pagebody-inner" class="pkg">
  31                <div id="alpha">
  32                   <div id="alpha-inner" class="pkg">
  33
  34                      <p class="content-nav">
  35                         <a href="http://defaria.com/blogs/Status/archives/week_2005_01_02.html">&laquo; January  2, 2005 - January  8, 2005</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2005_01_16.html">January 16, 2005 - January 22, 2005 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">January 13, 2005</h2>
  44                      <a id="a000280"></a>
  45                      <div class="entry" id="entry-280">
  46                         <h3 class="entry-header">Native PPC toolchain build</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50   <li>Attempting to build PPC toolchain natively</li>
  51 </ul>
  52
  53                               <p>Although some errors persisted in the 120604-C build I decided it was time to at least try a native PPC build of the toolchain. The problem here is the PPC machine that I was told to use, t-mcpn765-1, is a LynxOS 4.0.0 machine! I don't think I'm supposed to try to build a 3.2.2 toolchain for 4.0.0.</p>
  54
  55 <p>Additionally, I've never built the toolchain natively on a PPC machine before. Previously, when building the toolchain natively, one needed to extract things like X/Motif (according to my instructions - which may very well be off base - why would we need X/Motif to build a compiler?!?) and devos (I think). Where do I get such things?</p>
  56
  57 <p>Additionally, t-mcpn765-1 doesn't have enough disk space.</p>
  58
  59                               <p class="entry-footer">
  60                                  <span class="post-footers">Posted by  at  4:48 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000280.html">Permalink</a>
  61
  62
  63                               </p>
  64                            </div>
  65                         </div>
  66                      </div>
  67
  68
  69
  70
  71                      <a id="a000279"></a>
  72                      <div class="entry" id="entry-279">
  73                         <h3 class="entry-header">Disk space problems & int_tools checkout</h3>
  74                         <div class="entry-content">
  75                            <div class="entry-body">
  76                               <ul>
  77   <li>Rebuilt PPC cross toolchain from 120604-B</li>
  78
  79   <li>Attempted to build 120604-C but ran out of diskspace on Dopey</li>
  80
  81   <li>Discovered source of problem with toolchain tarball naming inconsistenies</li>
  82 </ul>
  83
  84                               <h3>Rebuilding of cross toolchain from 120604-B</h3>
  85
  86 <p>After building LynxOS 120604-B and only receiving a few errors about (see previous days entry) I decided to attempt to rebuild the toolchain again. This seemed to work OK!</p>
  87
  88 <h3>Building LynxOS 120604-C</h3>
  89
  90 <p>With the toolchain rebuilt I went to rebuild LynxOS 120604-C. At this point Dopey ran out of disk space. I moved the 120604-A subdirectory over to /export/build2/defaria temporarily because that filesystem had much more space.</p>
  91
  92 <h3>Toolchain tarball naming change</h3>
  93
  94 <h4>AKA, why one should always cvs checkout int_tools instead of just copying it</h4>
  95
  96 <p>There's been this nagging problem of int_tools not being able to find the proper toolchain tarball to install compilers. This we due to the fact that I've been copying int_tools from 120604-A -> 120604-B -> 120406-C. Well names have changed but the copies of int_tools didn't reflect that change! Plus, for some reason, somebody hand fixed 120604-B but 120604-C and -A had been refreshed from CVS. Moral of this story is to always use cvs checkout to get a fresh copy of int_tools.</p>
  97
  98 <div class="note">
  99   <p><b>Note:</b> This underscores one of the things that I do not like in CVS, that being the tendency of making many copies of what's in CVS due to it's snapshot view/sandbox like methodology. It's easy to see where one might create a 120604-C/int_tools directory via a cvs checkout int_tools and that int_tools be different than 120604-B and 120604-C's copies. If one then needs to make a change to int_tools and this change should apply to the -B and -C areas as well then one needs to remember about the -B and -C areas and remember to update them as well. This is a common problem with a snapshot/sandbox philosophy. Nevermind that it's wasteful to have so many multiple copies of essentially the same thing - wasteful in terms of diskspace and prone to misunderstanding and human error.</p>
 100 </div>
 101
 102                               <p class="entry-footer">
 103                                  <span class="post-footers">Posted by  at  2:54 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000279.html">Permalink</a>
 104
 105
 106                               </p>
 107                            </div>
 108                         </div>
 109                      </div>
 110
 111
 112
 113                      <h2 class="date-header">January 12, 2005</h2>
 114                      <a id="a000278"></a>
 115                      <div class="entry" id="entry-278">
 116                         <h3 class="entry-header">PPC Builds</h3>
 117                         <div class="entry-content">
 118                            <div class="entry-body">
 119                               <ul>
 120   <li>Built PPC Toolchain with 120604-A</li>
 121
 122   <li>Attempting to build 120604-B with this new toolchain</li>
 123 </ul>
 124
 125                               <p>Adam helped me figure out that the reason that the toolchain was failing to build was because the ppc/lib directory in 120604-B didn't have the proper libraries. I proceeded to build the tookchain using 120604-A.</p>
 126
 127 <p>After successfully building the toolchain in 120604-A I proceeded to attempt to build LynxOS in 120604-B utilizing int_tools. The first problem that I had was that it attempts to install a compiler from DIR_PATH(compilers), which was set to 3.2.2-120604. But the toolchain I built for PPC was not there. Note that there was also a 3.2.2-122804 directory. I decided to use 3.2.2-122804 instead of 3.2.2-120604 and I scp'ed the toolchain I built over to that directory. The 3.2.2-122804 already had some toolchains in there but didn't have PPC toolchains.</p>
 128
 129 <p>After performing a make package for the toolchain I wound up with a toolchain-i686-pc-linux-gnu-powerpc.tar.gz. So I copied that over to 3.2.2-122804. But int_tools was looking for a toolchain-i-686-pc-linux-gnu-ppc.tar.gz. I solved this problem by symlinking. I also needed a toolchain-powerpc-lynx-lynxos-ppc.tar.gz or int_tools complained.</p>
 130
 131 <p>After fixing those problem I managed to build LynxOS but there were a few errors:</p>
 132
 133 <div class="code"><pre>
 134 LOGS/makeall.log:make[5]: *** [/usr/lynx/5.0.0/ppc/sys/family.ppc/lib/libdrivers.a(flopdrvr.o)] Error 1
 135 LOGS/makeall.log:make[4]: *** [/usr/lynx/5.0.0/ppc/sys/family.ppc/lib/libdrivers.mpc8260_vads.a(flash_mtd_vads.o)] Error 1
 136 LOGS/makeall.log:make[3]: *** [common_all] Error 1
 137 LOGS/makeall.log:make[4]: *** [/usr/lynx/5.0.0/ppc/sys/family.ppc/lib/libdrivers.rpxl823.a(flopdrvr.o)] Error 1
 138 LOGS/makeall.log:make[4]: *** [/usr/lynx/5.0.0/ppc/sys/family.ppc/lib/libdrivers.vmpc.a(flopdrvr.o)] Error 1
 139 LOGS/makeall.log:make[4]: *** [/usr/lynx/5.0.0/ppc/sys/family.ppc/lib/libdrivers.vmpc.a(if_dec21040.o)] Error 1
 140 </pre></div>
 141
 142 <p>There are also some errors in demo.log.</p>
 143
 144 <p>Are these reasonable errors? Should I go one to attempt to build the PPC toolchain again using this LynxOS?</p>
 145
 146                               <p class="entry-footer">
 147                                  <span class="post-footers">Posted by  at  3:11 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000278.html">Permalink</a>
 148
 149
 150                               </p>
 151                            </div>
 152                         </div>
 153                      </div>
 154
 155
 156
 157                      <h2 class="date-header">January 11, 2005</h2>
 158                      <a id="a000277"></a>
 159                      <div class="entry" id="entry-277">
 160                         <h3 class="entry-header">PPC Toolchain build</h3>
 161                         <div class="entry-content">
 162                            <div class="entry-body">
 163                               <ul>
 164   <li>Restarted building PPC toolchain cross</li>
 165 </ul>
 166
 167                               <p>Adam correctly pointed out that 120604-B had relatively nothing in $ENV_PREFIX/lib. I don't know what that's so empty but 120604-A had a more full $ENV_PREFIX/lib so we switched over to using that.</p>
 168
 169                               <p class="entry-footer">
 170                                  <span class="post-footers">Posted by  at  5:33 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000277.html">Permalink</a>
 171
 172
 173                               </p>
 174                            </div>
 175                         </div>
 176                      </div>
 177
 178
 179
 180
 181                      <a id="a000276"></a>
 182                      <div class="entry" id="entry-276">
 183                         <h3 class="entry-header">The Mysterious RSync Process</h3>
 184                         <div class="entry-content">
 185                            <div class="entry-body">
 186                               <ul>
 187   <li>Documented the rsync process</li>
 188
 189   <li>Documented the <i>Dopey Archives</i></li>
 190 </ul>
 191
 192                               <p>The mysterious rsync process has been found! Apparently the int_tools START process cannot write directly to T3's dev_archive area. So, instead it puts it to DIR_PATH(archive) which needs to reside on dopey and then an rsync script, in ~int/toosl/rsync_500.sh, to copy the files over to the official dev_archive area on T3</p>
 193
 194 <p>The psuedo archives, AKA <i>The Dopey Archvies</i> are pointed to by DIR_PATH(archive), typically at /export/build1/LYNXOS_500/archive.</p>
 195
 196                               <p class="entry-footer">
 197                                  <span class="post-footers">Posted by  at  4:13 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000276.html">Permalink</a>
 198
 199
 200                               </p>
 201                            </div>
 202                         </div>
 203                      </div>
 204
 205
 206
 207                      <h2 class="date-header">January 10, 2005</h2>
 208                      <a id="a000275"></a>
 209                      <div class="entry" id="entry-275">
 210                         <h3 class="entry-header">Documentation</h3>
 211                         <div class="entry-content">
 212                            <div class="entry-body">
 213                               <p>Added more structure to the documentation by including things I've developed at home with PHP. Mainly added a menu on the left hand side so as to allow easier navigation of the pages.</p>
 214
 215                               <p class="entry-footer">
 216                                  <span class="post-footers">Posted by  at  5:05 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000275.html">Permalink</a>
 217
 218
 219                               </p>
 220                            </div>
 221                         </div>
 222                      </div>
 223
 224
 225
 226
 227                      <a id="a000274"></a>
 228                      <div class="entry" id="entry-274">
 229                         <h3 class="entry-header">TOT Build succeeds</h3>
 230                         <div class="entry-content">
 231                            <div class="entry-body">
 232                               <p>After Moscow fixed the atoi error I believe that the TOT build succeeded!</p>
 233
 234                               <p>How does one determine if a build it successful? I ask because sometimes some errors are considered OK. But I don't know how to determine whether an error is acceptable or not. Here's the errors that I'm getting in the TOT build after Moscow has fixed the atoi error:</p>
 235
 236 <div class="code"><pre>
 237 LOGS/demo.log:make[1]: *** [hello_world] Error 1
 238 LOGS/demo.log:make[3]: *** [demo] Error 1
 239 LOGS/demo.log:make[2]: *** [demo/demo] Error 2
 240 LOGS/demo.log:make[1]: *** [local] Error 2
 241 LOGS/demo.log:make[1]: *** [hello_world] Error 1
 242 LOGS/demo.log:make[3]: *** [demo] Error 1
 243 LOGS/demo.log:make[2]: *** [demo/demo] Error 2
 244 LOGS/demo.log:make[1]: *** [local] Error 2
 245 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 246 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 247 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 248 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 249 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 250 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 251 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 252 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 253 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 254 LOGS/makeall.log:make[2]: *** [rkjump.o] Error 127
 255 LOGS/makeall.log:make[2]: *** No rule to make target `install'.  Stop.
 256 </pre></div>
 257
 258 <p>I figure the demo.log errors may be acceptable and I remember the [rkjump.o] error. But are those "No rule to make target 'install'"'s OK?</p>
 259
 260                               <p class="entry-footer">
 261                                  <span class="post-footers">Posted by  at 11:51 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000274.html">Permalink</a>
 262
 263
 264                               </p>
 265                            </div>
 266                         </div>
 267                      </div>
 268
 269                   </div>
 270                </div>
 271             </div>
 272          </div>
 273       </div>
 274    </div>
 275 </body>
 276 </html>