defaria.com/blogs/Status/archives/week_2005_05_08.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: May  8, 2005 - May 14, 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_05_01.html" title="May  1, 2005 - May  7, 2005" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2005_05_15.html" title="May 15, 2005 - May 21, 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_05_01.html">&laquo; May  1, 2005 - May  7, 2005</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2005_05_15.html">May 15, 2005 - May 21, 2005 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">May 13, 2005</h2>
  44                      <a id="a000355"></a>
  45                      <div class="entry" id="entry-355">
  46                         <h3 class="entry-header">LOS178 TOT Build</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50   <li>Attempted to build LOS178 TOT which is failing</li>
  51
  52   <li>Attempted to build LOS 178 TOT for Linux cross. Also failing</li>
  53
  54   <li>Updated <i>FCS ICS Hybrid OS Build Procedure</i> document</li>
  55 </ul>
  56
  57                               <p class="entry-footer">
  58                                  <span class="post-footers">Posted by  at  5:45 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000355.html">Permalink</a>
  59
  60
  61                               </p>
  62                            </div>
  63                         </div>
  64                      </div>
  65
  66
  67
  68                      <h2 class="date-header">May 11, 2005</h2>
  69                      <a id="a000354"></a>
  70                      <div class="entry" id="entry-354">
  71                         <h3 class="entry-header">CVS Reports</h3>
  72                         <div class="entry-content">
  73                            <div class="entry-body">
  74                               <ul>
  75   <li>Implemented many improvements to cvs_report.pl</li>
  76
  77   <li>Implemented some improvements to cvsr.php</li>
  78
  79   <li>Re-performed steps 1, 8-12 of BC build in order to pickup changes to tests and demos. Made new images available at <a href="ftp://saturn">ftp://saturn</a>.
  80 </ul>
  81
  82                               <h3>CVS Report Improvements</h3>
  83
  84 <p>Main problem addressed is that certain ECRs (or CRs) would show up if they were imported from a <i>vendor</i> branch. In general handling of revisions on branchs were not working very well. Other improvements include:</p>
  85
  86 <ul>
  87   <li>Changed to use Display package</li>
  88
  89   <li>While cvs_report.pl tries to avoid doing cvs update or recreating the cvs area it is possible that tags could move thus cvs_report.pl should refresh the cvs area in case the baseline tag has moved.</li>
  90
  91   <li>The special tag HEAD is ill defined under CVS. If a file is branched and the baseline tag is on the branch then it turns out that HEAD means the branch's head (this is with cvs diff only). If the file's baseline tag is on the trunk then HEAD means the trunk's head. Additionally the special revision 1.1.1 means <i>vendor</i> branch and is an alias for 1.1. This special situation is now better handled.</li>
  92
  93   <li>Changed the cvs diff --brief to use both from and to tags. Initially it was thought that if from tag didn't exist then cvs diff would complain about that. It does - sometimes. Ah the consistancy of cvs! Gotta love it! Still it's thought that it's better (clearer) to specify both from and to tags</li>
  94
  95   <li>Detection of no change is now better handled</li>
  96 </ul>
  97
  98 <h3>cvsr.php Improvements</h3>
  99
 100 <ul>
 101   <li>Now properly reports the latest revision when multiple revisions are checked in for the same ECR</li>
 102
 103    <li>Changed to return 2 character status, one indicating if the file is new and one to indicate if the file has changed (since the last report). This allows us to have a new and changed file.</li>
 104 </ul>
 105
 106                               <p class="entry-footer">
 107                                  <span class="post-footers">Posted by  at 12:36 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000354.html">Permalink</a>
 108
 109
 110                               </p>
 111                            </div>
 112                         </div>
 113                      </div>
 114
 115
 116
 117                      <h2 class="date-header">May 10, 2005</h2>
 118                      <a id="a000353"></a>
 119                      <div class="entry" id="entry-353">
 120                         <h3 class="entry-header">BC 5.3 on RH 8.0</h3>
 121                         <div class="entry-content">
 122                            <div class="entry-body">
 123                               <p>Wrote the following to Sasha today:</p>
 124
 125 <p>I'm still trying to build BC on RH 8.0. Since I was successful at building BC 5.3 on RH 6.1 I figured I oughta try building BC 5.3 on RH 8.0. I am also building starting as root.</p>
 126
 127 <p>I've tried twice now and it continues to fail in step 4.1 building the kernel. The following appears in build_kernel.log:</p>
 128 <div class="code"><pre>
 129 + echo BUILDING A KERNEL FOR pmac_g5...
 130 + cp /build/bluecat/build/20050429/cdt/src/bluecat/SOURCES/bluecat-pmac_g5.config arch/ppc/defconfig
 131 + rm -f .config
 132 + make mrproper
 133 + make oldconfig
 134 /bin/sh: line 1: bc_native_gcc: command not found
 135 make[1]: *** [scripts/basic/fixdep] Error 127
 136 make: *** [scripts_basic] Error 2
 137 error: Bad exit status from /build/bluecat/build/20050429/var/tmp/rpm-tmp.94728 (%build)
 138     Bad exit status from /build/bluecat/build/20050429/var/tmp/rpm-tmp.94728 (%build)
 139 </pre></div>
 140 <p>Apparently var/tmp/rpm-tmp.94728 is a build script built on the fly then executed. bc_native_gcc does exist in /usr/src/bluecat/eng/bluecat/bc_misc but this script can't find it.</p>
 141
 142 <p>Ideas?</p>
 143
 144                               <p class="entry-footer">
 145                                  <span class="post-footers">Posted by  at  9:22 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000353.html">Permalink</a>
 146
 147
 148                               </p>
 149                            </div>
 150                         </div>
 151                      </div>
 152
 153
 154
 155                      <h2 class="date-header">May  9, 2005</h2>
 156                      <a id="a000352"></a>
 157                      <div class="entry" id="entry-352">
 158                         <h3 class="entry-header">CVS Report bug</h3>
 159                         <div class="entry-content">
 160                            <div class="entry-body">
 161                               <p>The more I look into CVS the less I understand. Perhaps you can help me...</p>
 162
 163 <p>For the file los178/sys/kernel/getmem.c I see the following:</p>
 164 <div class="code"><pre>
 165 saturn:cvs log getmem.c
 166
 167 RCS file: /cvs/los178-cvs/los178/sys/kernel/getmem.c,v
 168 Working file: getmem.c
 169 head: 1.2
 170 branch:
 171 locks: strict
 172 access list:
 173 symbolic names:
 174        DEV_LOS178_2p1p0_ppc_20050503: 1.1.1.1.2.1
 175        REL_LOS178_2p0p0-branch: 1.1.1.1.0.4
 176                  ...
 177        REL_LOS178RSC_2p0p0_ppc_FCS: 1.1.1.1
 178                  ...
 179 saturn:cvs st getmem.c
 180 ===================================================================
 181 File: getmem.c          Status: Up-to-date
 182
 183   Working revision:    1.1.1.1
 184   Repository revision: 1.1.1.1 /cvs/los178-cvs/los178/sys/kernel/getmem.c,v
 185   Sticky Tag:          REL_LOS178_2p0p0_ppc_FCS (revision: 1.1.1.1)
 186   Sticky Date:         (none)
 187   Sticky Options:      -ko
 188 </pre></div>
 189 <p>In particular here notice that head says 1.2 but the current working revision is 1.1.1.1. The CVS Report does a:</p>
 190 <div class="code"><pre>
 191 saturn:cvs diff --brief -r HEAD getmem.c
 192 saturn:
 193 </pre></div>
 194 <p>Does this mean that there is no difference between 1.1.1.1 and 1.2?!? However if I do:</p>
 195 <div class="code"><pre>
 196 saturn:cvs diff --brief -r 1.2 getmem.c
 197 Index: getmem.c
 198 ===================================================================
 199 RCS file: /cvs/los178-cvs/los178/sys/kernel/getmem.c,v
 200 retrieving revision 1.2
 201 retrieving revision 1.1.1.1
 202 diff --brief -r1.2 -r1.1.1.1
 203 Files /tmp/cvsvGa4M1 and /tmp/cvswGa4M1 differ
 204 saturn:
 205 </pre></div>
 206 <p>Why is this so? Doesn't -r HEAD mean 1.2 in this instance?</p>
 207
 208                               <p class="entry-footer">
 209                                  <span class="post-footers">Posted by  at  2:59 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000352.html">Permalink</a>
 210
 211
 212                               </p>
 213                            </div>
 214                         </div>
 215                      </div>
 216
 217                   </div>
 218                </div>
 219             </div>
 220          </div>
 221       </div>
 222    </div>
 223 </body>
 224 </html>