gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From g...@vmgump.apache.org
Subject BATCH: All dressed up, with nowhere to go...
Date Tue, 25 Mar 2008 23:45:59 GMT
Dear Gumpmeisters,
            
The following 1 notifys should have been sent

*********************************************************** G U M P
[GUMP@vmgump]: Project logging-log4cxx-configure (in module logging-log4cxx) failed
*********************************************************** G U M P
[GUMP@vmgump]: Project logging-log4cxx-configure (in module logging-log4cxx) failed
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general@gump.apache.org.

Project logging-log4cxx-configure has an issue affecting its community integration.
This issue affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - logging-log4cxx-configure :  Apache log4cxx
    - logging-log4cxx-make :  Apache log4cxx
    - logging-log4cxx-make-install :  Apache log4cxx


Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4cxx/logging-log4cxx-configure/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4cxx/logging-log4cxx-configure/gump_work/buildscript_logging-log4cxx_logging-log4cxx-configure.html
Work Name: buildscript_logging-log4cxx_logging-log4cxx-configure (Type: Build)
Work ended in a state of : Failed
Elapsed: 34 secs
Command Line: /srv/gump/public/workspace/logging-log4cxx/configure --with-apr-util=/srv/gump/public/workspace/apr-util/dest-25032008
--with-apr=/srv/gump/public/workspace/apr/dest-25032008 --prefix=/srv/gump/public/workspace/logging-log4cxx/dest-25032008

[Working Directory: /srv/gump/public/workspace/logging-log4cxx]
---------------------------------------------
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from ccache gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if ccache gcc supports -fno-rtti -fno-exceptions... no
checking for ccache gcc option to produce PIC... -fPIC
checking if ccache gcc PIC flag -fPIC works... yes
checking if ccache gcc static flag -static works... yes
checking if ccache gcc supports -c -o file.o... yes
checking whether the ccache gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or
directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by ccache g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the ccache g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for ccache g++ option to produce PIC... -fPIC
checking if ccache g++ PIC flag -fPIC works... yes
checking if ccache g++ static flag -static works... yes
checking if ccache g++ supports -c -o file.o... yes
checking whether the ccache g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or
directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether ccache g++ accepts -g... (cached) yes
checking dependency style of ccache g++... (cached) gcc3
checking how to run the C++ preprocessor... ccache g++ -E
checking for doxygen... no
checking for APR... yes
checking for APR-util... configure: error: the --with-apr-util parameter is incorrect. It
must specify an install prefix, a build directory, or an apu-config file.
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/logging-log4cxx/logging-log4cxx-configure/rss.xml
- Atom: http://vmgump.apache.org/gump/public/logging-log4cxx/logging-log4cxx-configure/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 20001625032008, vmgump:vmgump-public:20001625032008
Gump E-mail Identifier (unique within run) #1.


--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message