Status for Andrew DeFaria

Bluecat build failing

Alexander Sanochkin wrote:

Andrew,

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).

Regarding the glib build problem we can not provide intelligent comments at this time as it seems that the 20050314 environment is not available for us on the jaguar machine.

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:

[int@jaguar loc_archive]$ diff do_it-bc5.0.orig do_it-bc5.0-gcc_3.4.3.orig
108c108
<   export BC_TARGET=$BLUECAT_TARGET_CPU-lynx-linux-bluecat
---
>   export BC_TARGET=$BLUECAT_TARGET_CPU-lynx-linux-gnubc

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?

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?

Build is still failing (on Jaguar). I get to step4 and it fails with:

Building glib package step 4.3 at 22:51:22
parse_file: build_package failed for glib_trg.spec
---- Step 4 finished successfully at Tue Mar 22 14:51:39 PST 2005 ----

Looking at step4/build_glib.log I see:

[int@jaguar step4]$ tail -f build_glib.log
+ ac_cv_func_getpwuid_r=yes
+ ac_cv_func_mutex_trylock=yes
+ ac_cv_func_cond_timedwait=yes
+ glib_cv_sizeof_gmutex=24
+ 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
+ ./configure --build=i386-linux-gnu --host=ppc-bluecat-linux
configure: warning: Could not determine POSIX flag. (-posix didn't work.)
configure: error: can not run test program while cross compiling
error: Bad exit status from /usr/lynx/loc_archive/build/20050319/var/tmp/rpm-tmp.40621 (%build)
    Bad exit status from /usr/lynx/loc_archive/build/20050319/var/tmp/rpm-tmp.40621 (%build)

Attempting to execute rpm-tmp.40621 reveals:

gcc -g -O2 -Wall -D_REENTRANT -o testglib testglib.o .libs/libglib.a
.libs/libglib.a(gmessages.o): In function `g_logv':
/usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10/gmessages.c:343: undefined reference to `va_copy'
.libs/libglib.a(gstrfuncs.o): In function `g_strdup_vprintf':
    /usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10/gstrfuncs.c:154: undefined reference to `va_copy'
collect2: ld returned 1 exit status
make[2]: *** [testglib] Error 1
make[2]: Leaving directory `/usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/lynx/loc_archive/build/20050319/cdt/src/bluecat/BUILD/glib-1.2.10'
make: *** [all-recursive-am] Error 2
+ exit 0

Any ideas?

Native PPC Toolchain failure

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:

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.

Meanwhile, we will ponder on what else can be wrong.