defaria.com/blogs/Status/archives/000279.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: Disk space problems & int_tools checkout</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/000278.html" title="PPC Builds" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000280.html" title="Native PPC toolchain build" />
  17
  18
  19
  20
  21
  22    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  23 </head>
  24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  25    <div id="container">
  26       <div id="container-inner" class="pkg">
  27
  28          <div id="banner">
  29             <div id="banner-inner" class="pkg">
  30                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  31                <h2 id="banner-description">Searchable status reports and work log</h2>
  32             </div>
  33          </div>
  34
  35          <div id="pagebody">
  36             <div id="pagebody-inner" class="pkg">
  37                <div id="alpha">
  38                   <div id="alpha-inner" class="pkg">
  39
  40                      <p class="content-nav">
  41                         <a href="http://defaria.com/blogs/Status/archives/000278.html">&laquo; PPC Builds</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000280.html">Native PPC toolchain build &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000279"></a>
  47                      <div class="entry" id="entry-279">
  48                         <h3 class="entry-header">Disk space problems & int_tools checkout</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52   <li>Rebuilt PPC cross toolchain from 120604-B</li>
  53
  54   <li>Attempted to build 120604-C but ran out of diskspace on Dopey</li>
  55
  56   <li>Discovered source of problem with toolchain tarball naming inconsistenies</li>
  57 </ul>
  58                            </div>
  59                            <div id="more" class="entry-more">
  60                               <h3>Rebuilding of cross toolchain from 120604-B</h3>
  61
  62 <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>
  63
  64 <h3>Building LynxOS 120604-C</h3>
  65
  66 <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>
  67
  68 <h3>Toolchain tarball naming change</h3>
  69
  70 <h4>AKA, why one should always cvs checkout int_tools instead of just copying it</h4>
  71
  72 <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>
  73
  74 <div class="note">
  75   <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>
  76 </div>
  77                            </div>
  78                         </div>
  79                         <p class="entry-footer">
  80                            <span class="post-footers">Posted by  on January 13, 2005  2:54 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000279.html">Permalink</a>
  81                         </p>
  82                      </div>
  83
  84
  85
  86
  87                   </div>
  88                </div>
  89             </div>
  90          </div>
  91       </div>
  92    </div>
  93 </body>
  94 </html>