defaria.com/blogs/Status/archives/week_2005_06_26.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: June 26, 2005 - July  2, 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_06_19.html" title="June 19, 2005 - June 25, 2005" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2005_07_03.html" title="July  3, 2005 - July  9, 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_06_19.html">&laquo; June 19, 2005 - June 25, 2005</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2005_07_03.html">July  3, 2005 - July  9, 2005 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">June 30, 2005</h2>
  44                      <a id="a000379"></a>
  45                      <div class="entry" id="entry-379">
  46                         <h3 class="entry-header">Building CDK on Windows</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50   <li>Investigated bug on Windows nmake of CDK</li>
  51
  52   <li>Fixed build_los178 to properly build LOS178 2.1</li>
  53 </ul>
  54
  55                               <h3>Windows nmake bug for CDK build</h3>
  56
  57 <p>There is still something wrong. Here's what I did:</p>
  58
  59 <ul>
  60   <li>Obtained the following tarballs from the 20050628 archive:
  61     <ul>
  62       <li>2000-00.los178_rsc_src.tar.gz</li>
  63
  64       <li>2001-00.los178_src.tar.gz</li>
  65
  66       <li>2013-00.los178_dev.tar.gz</li>
  67
  68       <li>2015-00.los178_rsc_dev.tar.gz</li>
  69     </ul>
  70   <li>Unpacked those tarballs + ppc.cdkwin32.tar.gz into /tmp/los178</li>
  71
  72   <li>Setup my environment properly (this includes VCVARS32.bat)</li>
  73
  74   <li>cd'ed to src/cdk and performed make install > install.log 2>&1</li>
  75 </ul>
  76
  77 <p>I still have the error:</p>
  78
  79 <div class="code"><pre>
  80     Compiling coff.o
  81     coff.c(87) : fatal error C1083: Cannot open include file: 'family/ppc/arch_mem.h': No such file or directory
  82     NMAKE : fatal error U1077: 'cl.exe' : return code '0x2'
  83     Stop.
  84     make[1]: *** [WIN32_VS_UTIL] Error 2
  85 </pre></div>
  86
  87 <p>It seems clear to me that the compiler cannot locate the include file family/ppc/arch_mem.h which does reside under $ENV_PREFIX/sys/include. Additionally it's clear that common/mkimage/Makefile was changed to append "-I$(ENV_PREFIX)/sys/include" to SPECIAL_CFLAGS to resolve this issue. However something on Windows (and Windows nmake) is causing this to remain a problem.</p>
  88
  89 <p>It seems that nmake eventually issues the following command to compile coff.c -> coff.o:</p>
  90
  91 <div class="code"><pre>
  92     cl.exe /nologo /ML /W3 /GX /D "_WIN32_VS" /D "_CONSOLE" /D "WIN32" /D "_MBCS" /FD /c -c coff.c -D__powerpc__ /Fo"coff.o"
  93 </pre></div>
  94
  95 <p>Which, of course, doesn't seem to mention $ENV_PREFIX/sys/include at all. IOW the above results in:</p>
  96
  97 <div class="code"><pre>
  98     cl.exe /nologo /ML /W3 /GX /D "_WIN32_VS" /D "_CONSOLE" /D "WIN32" /D "_MBCS" /FD /c -c coff.c -D__powerpc__ /Fo"coff.o"
  99     coff.c
 100     coff.c(87) : fatal error C1083: Cannot open include file: 'family/ppc/arch_mem.h': No such file or directory
 101 </pre></div>
 102
 103 <p>While the following results in a successful compilation (with warnings):</p>
 104
 105 <div class="code"><pre>
 106     cl.exe /nologo /ML /W3 /GX /D "_WIN32_VS" /D "_CONSOLE" /D "WIN32" /D "_MBCS" /FD /c -c coff.c -D__powerpc__ /Fo"coff.o" /I$ENV_PREFIX/sys/include
 107 </pre></div>
 108
 109 <p>The Makefile and Windows nmake are not arranging for SPECIAL_CFLAGS to be passed along to the compiler.</p>
 110
 111 <h3>Fix to build_los178</h3>
 112
 113 <p>The build_los178 script was having a problem building LOS178. It would fail in different ways than when done from the command line. I suspected the problem would be in the setup_bash function as it attempts to reproduce what a ". SETUP.bash" does inside the Perl environment. Turns out I was right. Changed that subroutine to properly set HOST_OS_REVISION (previously it had an extra carriage return from `uname -r`) and to add /usr/ucb to the PATH.</p>
 114
 115                               <p class="entry-footer">
 116                                  <span class="post-footers">Posted by  at 10:21 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000379.html">Permalink</a>
 117
 118
 119                               </p>
 120                            </div>
 121                         </div>
 122                      </div>
 123
 124
 125
 126                      <h2 class="date-header">June 28, 2005</h2>
 127                      <a id="a000378"></a>
 128                      <div class="entry" id="entry-378">
 129                         <h3 class="entry-header">Built LOS178 2.1.0 TOB</h3>
 130                         <div class="entry-content">
 131                            <div class="entry-body">
 132                               <ul>
 133   <li>Completed the build of LOS178 2.1.0 TOB and released it to t3:/export/dev_archive/los178/2p1p0/20050628</li>
 134
 135   <li>Updated cvs_report to not report duplicate entries. This can occur when somebody say checks in foo.c thus creating revision 1.2 for CR 40 and then checks in foo.c again, thus creating revision 1.3. Before cvs_report would report foo.c twice. Now it just reports the highest revision (e.g. 1.3).</li>
 136
 137   <li>Updated cvs_report to take another parameter, -cvsr, for a cvs report area. cvs_report uses this area in order to determine what to report. Contained in this area is a .cvsr file which holds the baseline tag. However if you want to report on both the main trunk and a branch then you can't use the same area. In the past cvs_report was oriented to using the module name for the area. Now you can specify an alternate area.</li>
 138 </ul>
 139
 140                               <p class="entry-footer">
 141                                  <span class="post-footers">Posted by  at  2:32 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000378.html">Permalink</a>
 142
 143
 144                               </p>
 145                            </div>
 146                         </div>
 147                      </div>
 148
 149                   </div>
 150                </div>
 151             </div>
 152          </div>
 153       </div>
 154    </div>
 155 </body>
 156 </html>