defaria.com/blogs/Status/archives/week_2005_08_21.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: August 21, 2005 - August 27, 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_08_14.html" title="August 14, 2005 - August 20, 2005" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2005_09_04.html" title="September  4, 2005 - September 10, 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_08_14.html">&laquo; August 14, 2005 - August 20, 2005</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2005_09_04.html">September  4, 2005 - September 10, 2005 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">August 26, 2005</h2>
  44                      <a id="a000415"></a>
  45                      <div class="entry" id="entry-415">
  46                         <h3 class="entry-header">portgd, 3.0.0 TOT build again</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50   <li>Portgd still not working well</li>
  51
  52   <li>Build 3.0.0 TOT again</li>
  53
  54   <li>Added package of pdn to 2.1.0. Somehow I missed it</li>
  55
  56   <li>Repackaged cdklinux</li>
  57 </ul>
  58
  59                               <h3>Portgd's continuing woes</h3>
  60
  61 <p>Turns out the problem is that we are attempting to do a cvs add from outside of the repository. Portgd works from one directory and checks out an los178.from and an los178.to. Then from that directory it attempts to cvs add los178.to/&lt;path&gt;/&lt;dir&gt;. This will not work. We need, instead, to cd los178.to then do cvs add &lt;path&gt;/&lt;dir&gt;.</p>
  62
  63 <p>But portgd was also having a problem trying to recursively add the directories above new files. How to debug/test this is the question...</p>
  64
  65                               <p class="entry-footer">
  66                                  <span class="post-footers">Posted by  at  5:00 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000415.html">Permalink</a>
  67
  68
  69                               </p>
  70                            </div>
  71                         </div>
  72                      </div>
  73
  74
  75
  76                      <h2 class="date-header">August 25, 2005</h2>
  77                      <a id="a000414"></a>
  78                      <div class="entry" id="entry-414">
  79                         <h3 class="entry-header">portgd, NetSNMP</h3>
  80                         <div class="entry-content">
  81                            <div class="entry-body">
  82                               <ul>
  83   <li>Changed portgd script to attempt to handle new CVS files/li>
  84
  85   <li>Changed package.sh for 3.0.0 to package NetSNMP</li>
  86
  87   <li>Release LOS178 2.1.0. Still working on building GDB on Windows</li>
  88
  89   <li>Built and released LOS178 3.0.0 20050825. Turns out the toolchain I was using does indeed have the latest!</li>
  90
  91   <li>Port of GD from LOS178 has some missing CRs. Will work on this tomorrow</li>
  92 </ul>
  93
  94                               <p class="entry-footer">
  95                                  <span class="post-footers">Posted by  at 12:43 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000414.html">Permalink</a>
  96
  97
  98                               </p>
  99                            </div>
 100                         </div>
 101                      </div>
 102
 103
 104
 105                      <h2 class="date-header">August 24, 2005</h2>
 106                      <a id="a000413"></a>
 107                      <div class="entry" id="entry-413">
 108                         <h3 class="entry-header">3.0.0 build, GD build</h3>
 109                         <div class="entry-content">
 110                            <div class="entry-body">
 111                               <ul>
 112   <li>Performed a TOT 3.0.0 build. More stuff coming in...</li>
 113
 114   <li>Struggling with 2.0 GD build. Turns out I was missing some CRs. Finally building!</li>
 115
 116   <li>GDB Server build on Solaris is OK now but it fails on Linux. I suspect a packaging problem</li>
 117
 118   <li>The portgd script has issues</li>
 119 </ul>
 120
 121                               <h3>Portgd Challenges</h3>
 122
 123 <p>One of the problems with portgd is that the from CVS repository really needs to be set to HEAD because you want the latest but you're gonna pull the CRs by number and individual file revisions. This may cause problems sometimes (think ordering of CR numbers where pulling one CR overwrites a previous one in the wrong way. BTW This is why branching is good!)</p>
 124
 125 <p>Additionally portgd has a problem where the CR introduces new elements (Clearcase term - think new files and/or directories). When portgd attempts to cp the file to the to CVS repository it may fail because the parent directory did not previously exist and is not in the to CVS repository.</p>
 126
 127 <p>The portgd script can be updated to check to insure that each directory in the path of the file revision to be "ported" exists and if not then to create it and add it to CVS. It should also check to see if the file is new and again copy it but also add it to CVS.</p>
 128
 129                               <p class="entry-footer">
 130                                  <span class="post-footers">Posted by  at 11:32 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000413.html">Permalink</a>
 131
 132
 133                               </p>
 134                            </div>
 135                         </div>
 136                      </div>
 137
 138
 139
 140                      <h2 class="date-header">August 22, 2005</h2>
 141                      <a id="a000411"></a>
 142                      <div class="entry" id="entry-411">
 143                         <h3 class="entry-header">Linux ABI build failure/GDB Build failure</h3>
 144                         <div class="entry-content">
 145                            <div class="entry-body">
 146                               <ul>
 147   <li>Linux ABI build fails. Reported to vlad</li>
 148
 149   <li>GDB build failed. Rebuilding...</li>
 150 </ul>
 151
 152                               <h3>Linux ABI build failure</h3>
 153
 154 <p>The Linux ABI fails to build on yellowdog Linux.</p>
 155
 156 <div class="code"><pre>
 157     + DebugFlags=
 158     + export GLIBC_LOCATION LYNX_PREFIX LIBLYNXPTHREAD_PREFIX
 159     + export LYNXOS_VERSION_MAJOR LYNXOS178_VERSION_MAJOR
 160     + '[' 1 '!=' 0 ']'
 161     + '[' '!' -r /home/int/LOS178-300/20050822/linuxabi/glibc-2.3.3/../liblynxpthrea
 162     d/Makefile ']'
 163     + echo ======================= BUILD - LIBLYNXPTHREAD ==========================
 164     ===========
 165     ======================= BUILD - LIBLYNXPTHREAD =================================
 166     ====
 167     + cd /home/int/LOS178-300/20050822/linuxabi/glibc-2.3.3/../liblynxpthread
 168     + make PLATFORM=ppc
 169     make: *** No rule to make target `include/itimer.h', needed by `all'.  Stop.
 170     + exit 1
 171 </pre></div>
 172
 173 <p>itimer.h has been removed. There are other problems too.</p>
 174
 175 <h3>GDB Build Failure</h3>
 176
 177 <p>For some reason it turns out that several libraries such as libc.a appear in the dev area as if they were built as production. IOW the size of libc.a(dev) == libc.a(pdn). Don't know why this happened because the install.log for dev seems to indicate that it was built in dev mode. May be a problem in the build_los178 script. Rebuilding...</p>
 178
 179 <p>Also, due to hardcoding of bison's location we must build in /usr/los178/2.1.0/ppc_dev.</p>
 180
 181                               <p class="entry-footer">
 182                                  <span class="post-footers">Posted by  at  6:10 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000411.html">Permalink</a>
 183
 184
 185                               </p>
 186                            </div>
 187                         </div>
 188                      </div>
 189
 190                   </div>
 191                </div>
 192             </div>
 193          </div>
 194       </div>
 195    </div>
 196 </body>
 197 </html>