defaria.com/blogs/Status/archives/000260.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: LOS178 Build/5.0.0 native toolchain build</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/000259.html" title="LOS178 &amp; ECR 23084" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000261.html" title="Improving fix_copyright.pl" />
  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/000259.html">&laquo; LOS178 & ECR 23084</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000261.html">Improving fix_copyright.pl &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000260"></a>
  47                      <div class="entry" id="entry-260">
  48                         <h3 class="entry-header">LOS178 Build/5.0.0 native toolchain build</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52
  53 <li>LOS178 build after copyright fix builds with 12 errors. Test build of LOS178 without copyright fix also builds with 12 errors!</li>
  54
  55 <li>Building of 5.0.0 toolchain natively is failing</li>
  56
  57 </ul>
  58                            </div>
  59                            <div id="more" class="entry-more">
  60                               <h3>LOS178 copyright fix</h3>
  61
  62 <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>
  63
  64 <p>The real difficulty is that there is no real standard in our copyright blocks thus it is hard to get this right</p>
  65
  66 <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>
  67
  68 <p>There were a number of files that this occurred in and they were hand edited</p>
  69
  70 <h3>5.0.0 Native Toolchain Build</h3>
  71
  72 <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>
  73
  74 <pre>
  75 Configuring texinfo...
  76 configure: error: invalid package name: gcc-version-trigger
  77 Configure in /mnt/toolchain/build-i386/texinfo failed, exiting.
  78 make: *** [stamp-configure-i386] Error 1
  79 </pre>
  80
  81 <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>
  82                            </div>
  83                         </div>
  84                         <p class="entry-footer">
  85                            <span class="post-footers">Posted by  on December 17, 2004 10:38 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000260.html">Permalink</a>
  86                         </p>
  87                      </div>
  88
  89
  90
  91
  92                   </div>
  93                </div>
  94             </div>
  95          </div>
  96       </div>
  97    </div>
  98 </body>
  99 </html>