Sriram Natarajan wrote:
> No, this is not an error. This is just a regular warning reported 
> because PHP build system officially supports autoconf 2.13 and we are 
> using autoconf 2.61. This warning will NOT cause the error that you 
> are seeing. The error you are seeing is some thing to do with 
> checkout. You could do some thing like wx reset && wx init -ft  
> followed by nightly -n .
I'm re-running the nightly now to see if that works.

Come back on this later.
Thanks Sriram,

----sunanda


>
> - Sriram
>
> sunanda menon wrote:
>> Sriram Natarajan wrote:
>>> Not sure what is causing the problem. In you case, did you try 
>>> bringing over the source from gate instead of from clone ? Also, you 
>>> could bring over the source and then run the nightly with -n and see 
>>> if that helps
>>>
>>> - Sriram
>> Digging into the logs ,I see this error message
>>
>> gmake[1]: Leaving directory 
>> `/export/home/sunanda/6857014/usr/src/cmd/openwsman/openwsman-2.1.0'
>> mkdir -p tmp;
>> (cd tmp; /usr/sfw/bin/gtar xjpf ../openwsman-2.1.0.tar.bz2 
>> --no-same-owner; )
>> mv tmp/openwsman-2.1.0 openwsman-2.1.0-64; rmdir tmp;
>> (cd openwsman-2.1.0-64; \
>>    /usr/bin/gpatch -p1 < ../openwsman.patch; \
>>    autoconf; )
>> patching file include/u/debug.h
>> patching file include/u/logprv.h
>> patching file include/u/os.h
>> patching file src/lib/wsman-soap.c
>> patching file src/server/shttpd/io.h
>> patching file src/server/shttpd/config.c
>> patching file configure.in
>> patching file src/lib/Makefile.am
>> patching file src/lib/Makefile.in
>> patching file src/cpp/Makefile.am
>> patching file src/cpp/Makefile.in
>> patching file src/server/Makefile.am
>> patching file src/server/Makefile.in
>> patching file src/lib/wsman-dispatcher.c
>> patching file src/lib/wsman-xml-serialize.c
>> aclocal.m4:16: warning: this file was generated for autoconf 2.61.
>> You have another version of autoconf.  It may work, but is not 
>> guaranteed to.
>> If you have problems, you may need to regenerate the build system 
>> entirely.
>> To do so, use the procedure documented by the package, typically 
>> `autoreconf'.
>> configure.in:106: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, 
>> ...): suspicious cache-id, must contain _cv_ to be cached
>> ../../lib/autoconf/general.m4:1974: AC_CACHE_VAL is expanded from...
>> ../../lib/autoconf/general.m4:1994: AC_CACHE_CHECK is expanded from...
>> aclocal.m4:647: AC_LIBTOOL_COMPILER_OPTION is expanded from...
>> aclocal.m4:4937: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
>> aclocal.m4:2717: _LT_AC_LANG_C_CONFIG is expanded from...
>> aclocal.m4:2716: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
>> aclocal.m4:94: AC_LIBTOOL_SETUP is expanded from...
>> aclocal.m4:74: _AC_PROG_LIBTOOL is expanded from...
>> aclocal.m4:39: AC_PROG_LIBTOOL is expanded from...
>> aclocal.m4:6482: AM_PROG_LIBTOOL is expanded from...
>> configure.in:106: the top level
>>


-- 
Sunanda Menon
Database Technology Group
BLR03, x87098/91-80-66937098
http://blogs.sun.com/smenon


Reply via email to