Initial add of defaria.com
[clearscm.git] / defaria.com / blogs / Status / archives / 000322.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: Bluecat build still failing</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/000318.html" title="NetSNMP/Native x86 toolchain problems/ECR Linkify" />
16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000321.html" title="LOS178 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/000318.html">&laquo; NetSNMP/Native x86 toolchain problems/ECR Linkify</a> |
42                         <a href="http://defaria.com/blogs/Status/">Main</a>
43                         | <a href="http://defaria.com/blogs/Status/archives/000321.html">LOS178 build &raquo;</a>
44                      </p>
45
46                      <a id="a000322"></a>
47                      <div class="entry" id="entry-322">
48                         <h3 class="entry-header">Bluecat build still failing</h3>
49                         <div class="entry-content">
50                            <div class="entry-body">
51                               <ul>
52   <li>Bluecat build still fails with same problem. Emailed Sasha</li>
53
54   <li>Native PPC Toolchain still failing - same problems</li>
55
56   <li>Recreated cvsr.php - file was previously deleted</li>
57 </ul>
58                            </div>
59                            <div id="more" class="entry-more">
60                               <h3>Bluecat build failing</h3>
61
62 <p>Alexander Sanochkin wrote:</p>
63
64 <blockquote>
65 <p>Andrew,</p>
66
67 <p>It seems you tried to use a build tag which was not ready to rebuild BlueCat at that time. Also please note that the main BC build script has changed due to updating the BC cross compiler to version 3.4.3. The script is called do_it-bc5.0-gcc_3.4.3. You can get it from the BlueCat CVS. (/cm/CVS/BlueCat/eng/int/scripts).</p>
68
69 <p>Regarding the glib build problem we can not provide intelligent comments at this time as it seems that the 20050314 environment
70 is not available for us on the jaguar machine.</p>
71 </blockquote>
72
73 <p>What build tag are we supposed to use? I found R_5_2_1_ppc_20050319 and I assume that is what I should use. However the difference between do_it-bc5.0-gcc_3.4.3 and do_it-bc5.0 is merely:</p>
74
75 <div class="code"><pre>
76 [int@jaguar loc_archive]$ diff do_it-bc5.0.orig do_it-bc5.0-gcc_3.4.3.orig
77 108c108
78 <   export BC_TARGET=$BLUECAT_TARGET_CPU-lynx-linux-bluecat
79 ---
80 >   export BC_TARGET=$BLUECAT_TARGET_CPU-lynx-linux-gnubc
81 </pre></div>
82
83 <p>And, if I might ask, why all the version numbers in the file? Why isn't it just named do_it and depending on which CVS (RCS?) tag you use you get a 5.0 or a 5.0-gcc_3.4.3 version?</p>
84
85 <p>Also, with do_it-bg5.0-gcc_3.4.3 I suspect that the changes I made for the patch-spec (changing do_step to perform patches between steps 1 and 2 when run in stepwise fashion) have not be incorporated. Seems to me that there are two steps being done in automated mode (i.e. doing all steps at one time) that are not performed when doing things in a stepwise fashion. The first is the building of the new GNU Tools which is effectively step 0 and the second is this patching thing which is normally done between steps 1 and 2. Might I suggest that we make these regular steps in their proper order and renumber the rest?</p>
86
87 <p>Build is still failing (on Jaguar). I get to step4 and it fails with:</p>
88
89 <div class="code"><pre>
90 Building glib package step 4.3 at 22:51:22
91 parse_file: build_package failed for glib_trg.spec
92 ---- Step 4 finished successfully at Tue Mar 22 14:51:39 PST 2005 ----
93
94 Looking at step4/build_glib.log I see:
95
96 [int@jaguar step4]$ tail -f build_glib.log
97 + ac_cv_func_getpwuid_r=yes
98 + ac_cv_func_mutex_trylock=yes
99 + ac_cv_func_cond_timedwait=yes
100 + glib_cv_sizeof_gmutex=24
101 + glib_cv_byte_contents_gmutex=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
102 + ./configure --build=i386-linux-gnu --host=ppc-bluecat-linux
103 configure: warning: Could not determine POSIX flag. (-posix didn't work.)
104 configure: error: can not run test program while cross compiling
105 error: Bad exit status from /usr/lynx/loc_archive/build/20050319/var/tmp/rpm-tmp.40621 (%build)
106     Bad exit status from /usr/lynx/loc_archive/build/20050319/var/tmp/rpm-tmp.40621 (%build)
107 </pre></div>
108
109 <p>Attempting to execute rpm-tmp.40621 reveals:</p>
110
111 <div class="code"><pre>
112 gcc -g -O2 -Wall -D_REENTRANT -o testglib testglib.o .libs/libglib.a
113 .libs/libglib.a(gmessages.o): In function `g_logv':
114 /usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10/gmessages.c:343: undefined reference to `va_copy'
115 .libs/libglib.a(gstrfuncs.o): In function `g_strdup_vprintf':
116     /usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10/gstrfuncs.c:154: undefined reference to `va_copy'
117 collect2: ld returned 1 exit status
118 make[2]: *** [testglib] Error 1
119 make[2]: Leaving directory `/usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10'
120 make[1]: *** [all-recursive] Error 1
121 make[1]: Leaving directory `/usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10'
122 make: *** [all-recursive-am] Error 2
123 + exit 0
124 </pre></div>
125
126 <p>Any ideas?</p>
127
128 <h3>Native PPC Toolchain failure</h3>
129
130 <p>Build of the Native PPC Toolchain keeps failing for me but not for Oleg. Oleg's been suggesting that I lower the ulimits to -s 100000 and -d 200000, which I did but which fails for me and not Oleg. Oleg writes:</p>
131
132 <blockquote>
133 <p>Perhaps the time of the day has some effect on the file system behaviour (or an increased local network activity during the business time has some adverse effect on the system stability). Please try to start the toolchain build at your end-of-business time.</p>
134
135 <p>Meanwhile, we will ponder on what else can be wrong.</p>
136 </blockquote>
137
138                            </div>
139                         </div>
140                         <p class="entry-footer">
141                            <span class="post-footers">Posted by  on March 22, 2005  4:44 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000322.html">Permalink</a>
142                         </p>
143                      </div>
144
145                      
146
147                      
148                   </div>
149                </div>
150             </div>
151          </div>
152       </div>
153    </div>
154 </body>
155 </html>