Ticket #537 (Closed: fixed)

can you state your autoheader / autoconf version? I persume it's not 2.5x...

[root@lnxsrv2 bin]# autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie? and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lnxsrv2 bin]# autoheader --version autoheader (GNU Autoconf) 2.59 Written by Roland McGrath? and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lnxsrv2 bin]#

great! aclocal / automake version? actually, from your output, the problem seems to lie with aclocal (which is part of automake)

[root@lnxsrv2 bin]# aclocal --version aclocal (GNU automake) 1.9.2 Written by Tom Tromey <[email protected]> Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lnxsrv2 bin]# [root@lnxsrv2 bin]# automake --version automake (GNU automake) 1.9.2 Written by Tom Tromey <[email protected]>. Copyright 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lnxsrv2 bin]#

herein lies the problem: these scripts assume automake 1.8 can you try, from the modules/core directory: export WANT_AUTOMAKE=1.8 bin/autogen.sh

[root@lnxsrv2 core]# export WANT_AUTOMAKE=1.8 [root@lnxsrv2 core]# bin/autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it, please specify them on the bin/autogen.sh command line. Generating configuration files for Core, please wait.... aclocal --output=/modules/core/tmp/aclocal.m4 acinclude.m4:39: warning: underquoted definition of PKG_CHECK_MODULES run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal /usr/share/aclocal/progsreiserfs.m4:13: warning: underquoted definition of AC_CHECK_LIBREISERFS /usr/share/aclocal/gob2.m4:7: warning: underquoted definition of GOB2_HOOK /usr/share/aclocal/cppunit.m4:4: warning: underquoted definition of AM_PATH_CPPUNIT autoheader /modules/core/etc/configure.ac aclocal.m4:14: /usr/bin/m4: Cannot open acinclude.m4: No such file or directory autom4te: /usr/bin/m4 failed with exit status: 1 autoheader: /usr/bin/autom4te failed with exit status: 1 autoconf -I /modules/core/tmp -o /modules/core/tmp/configure /modules/core/etc/configure.ac aclocal.m4:14: /usr/bin/m4: Cannot open acinclude.m4: No such file or directory autom4te: /usr/bin/m4 failed with exit status: 1 bin/autogen.sh: line 94: /modules/core/tmp/configure: No such file or directory [root@lnxsrv2 core]#

strange... after export WANT_AUTOMAKE=1.8 what does automake --version say? is it 1.8 or 1.9?

[root@lnxsrv2 core]# automake --version automake (GNU automake) 1.9.2 Written by Tom Tromey <[email protected]>. Copyright 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lnxsrv2 core]#

ok, here's the problem what I see on RedHat?, is that /usr/bin/automake is an exact copy of /usr/bin/automake-1.9. whereas on other systems, you can influence which automake to invoke by using some mechanism, like the WANT_AUTOMAKE environment variable. as a swift workaround, can you replace the command 'aclocal' with 'aclocal-1.7', e.g. change the line: cd ${etcdir} && aclocal $ACLOCAL_FLAGS ; cd ${tmpdir} to: cd ${etcdir} && aclocal-1.7 $ACLOCAL_FLAGS ; cd ${tmpdir} and see what happens? (it's also very strange, that RedHat? has aclocal 1.4 .. 1.7 and 1.9, but not 1.8)

I hope this is oke?, ACLOCAL_FLAGS="--output=${aclocal_m4}" echo " aclocal $ACLOCAL_FLAGS" #cd ${etcdir} && aclocal $ACLOCAL_FLAGS ; cd ${tmpdir} cd ${etcdir} && aclocal-1.7 $ACLOCAL_FLAGS ; cd ${tmpdir} echo " autoheader ${configure_ac}" autoheader ${configure_ac} echo " autoconf -I ${tmpdir} -o ${configure} ${configure_ac}" autoconf -I ${tmpdir} -o ${configure} ${configure_ac} [root@lnxsrv2 core]# bin/autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it, please specify them on the bin/autogen.sh command line. Generating configuration files for Core, please wait.... aclocal --output=/modules/core/tmp/aclocal.m4 autoheader /modules/core/etc/configure.ac autoconf -I /modules/core/tmp -o /modules/core/tmp/configure /modules/core/etc/configure.ac checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking time.h usability... yes checking time.h presence... yes checking for time.h... yes checking for pkg-config... /usr/bin/pkg-config checking for libxml++-2.6 >= 2.6.0... yes checking LIBXMLPP_CFLAGS... -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking LIBXMLPP_LIBS... -lxml++-2.6 -lxml2 -lpthread -lz -lm -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0 not compiling in code coverage mode configure: creating ./config.status config.status: creating ../Makefile config.status: creating configure.h [root@lnxsrv2 core]#

yes, this all seems OK. now, you could try a: make all and then: make check to see if all works fine. (provided that you've compiled the necessary libraries used by LiveSupport by running a 'make setup' in the livesupport directory earlier, as described in the getting started document, livesupport/doc/gettingStarted.html) as for invoking the correct version of aclocal, I'll figure out a way to change the scripts...

I think i have to wait becourse the main makefile now stop's with make modules_setup command for the next module. autoheader /modules/authentication/etc/configure.ac aclocal.m4:14: /usr/bin/m4: Cannot open acinclude.m4: No such file or directory autom4te: /usr/bin/m4 failed with exit status: 1 autoheader: /usr/bin/autom4te failed with exit status: 1 autoconf -I /modules/authentication/tmp -o /modules/authentication/tmp/configure /modules/authentication/etc/configure.ac aclocal.m4:14: /usr/bin/m4: Cannot open acinclude.m4: No such file or directory autom4te: /usr/bin/m4 failed with exit status: 1 ./modules/authentication/bin/autogen.sh: line 93: /modules/authentication/tmp/configure: No such file or directory make: *** [modules_setup] Error 127

this means that you've gone through successfully with the tools_setup target, and you're OK with the core module. (the error seen here has probably the same causes as the original error) so you can try to compile the core module now... but I still have to fix the scripts with regards to the specific automake versions..

Is it be posable to delete automake and copy automake-1.7 to automake?

I'd recommend the following: mkdir ~/bin cp /usr/bin/aclocal-1.7 ~/bin/aclocal cp /usr/bin/automake-1.7 ~/bin/automake export PATH=~/bin:$PATH (basically copy the 1.7 version of automake tools to ~/bin (the bin directory under your home directory), and prepend that location to the PATH environment varaiable. after this, this automake and aclocal should get invoked, try: automake --version which automake (the latter should point to ~/bin/automake)

Yes - but .... [root@lnxsrv2 bin]# mkdir ~/bin [root@lnxsrv2 bin]# cp /usr/bin/aclocal-1.7 ~/bin/aclocal [root@lnxsrv2 bin]# cp /usr/bin/automake-1.7 ~/bin/automake [root@lnxsrv2 bin]# export PATH=~/bin:$PATH [root@lnxsrv2 bin]# automake --version automake (GNU automake) 1.7.9 Written by Tom Tromey <[email protected]>. Copyright 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [root@lnxsrv2 bin]# I am going to fast - with a make all in the /modules/core dir i stil have a problem [root@lnxsrv2 core]# make all g++ -I/usr/include -g -O2 -DHAVE_CONFIG_H -pthread -pedantic -Wall -Wno-long-long -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I./../../usr/include -I./../../usr/include/boost-1_31 -I./include -I./tmp -c -o tmp/UniqueId?.o src/UniqueId?.cxx g++ -I/usr/include -g -O2 -DHAVE_CONFIG_H -pthread -pedantic -Wall -Wno-long-long -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I./../../usr/include -I./../../usr/include/boost-1_31 -I./include -I./tmp -c -o tmp/Playable.o src/Playable.cxx In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:22, from ./include/LiveSupport/Core/AudioClip?.h:45, from src/Playable.cxx:32: /usr/include/libxml++-2.6/libxml++/validators/validator.h:25: error: extra `;' make: *** [tmp/Playable.o] Error 1

yes, you should run bin/autogen.sh again, after having the tools compiled (as a result of make setup). please note, that make setup should have been the first thing done in the livesupport directory. our modules expect Xml++ version 2.8 (which is compiled at make setup), whereas your system seems to have 2.6? the very reason we've included specific versions of these libraries is to avoid such interoperability issues. after running bin/autogen.sh again, your build environment should refer to livesupport/usr/include/libxml++-2.6, etc. instead of /usr/include/libxml++-2.6

Thanks - i am going check the 2.6 vs 2.8 out

on Nov 30, 2004 is my error of the extra ; is be changed in de code Commit by murrayc :: libxml++/ (3 files in 2 dirs): * libxml++/validator.h: Removed an extra ; that g++ 3.4 complains about. on Dec 20, 2004 is version 2.8.1 releast and be available on http://ftp.gnome.org/pub/GNOME/sources/libxml++/2.8/

cool... I'll update it tomorrow...

OK, I've added libxml++ 2.8.1. from the livesupport directory, try: ./tools/libxml++/libxml++-2.8.1/bin/install.sh which should install it. then: cd modules/core ./bin/autogen.sh make see what happens :)

I have reinstalled my totaly system today, and start on this system with a fresh install. Fedora core 3 system is be so to slow of all things i have done the past day. Linux compiling its still a prosses of leaning. I am goining step by step. The 1e warning; The source of boost is be pointing to /usr/local a.s. /usr for python. For fedora core 3 i have put export line in the ./install.sh of boost export PYTHON_ROOT="/usr" export PYTHON_VERSION="2.3" export PYTHON_LIB_PATH="/usr/lib/python2.3/config" export PYTHON_INCLUDES="/usr/include/python2.3" The 2e warning; The source of cppunit is be warning about; no matching class member found for; `CPPUNIT_SOURCELINE' is not documented. Illegal command see as part of a \link; Unsupported html tag <failedtest> found ; Found unknown command; etc..etc Do i need to attach the log of the cppunit ./install.sh.

for the first problem: quite strange... more so, since boost has compiled for you earlier, hasn't it? the second issue: I guess those messages come up when CPPUNIT is generating its documentation via doxygen. I guess you can just ignore these messages...

Of boost - yes it's was be earlier a problem and now is be documented. Of cppunit - it's not the doxygen story. I am generating a log file now.

The problem starts with; Parsing file /livesupport/livesupport/tool s/cppunit/cppunit-1.10.2/tmp/cppunit-1.10.2/include/cppunit/SourceLine? .h:14: Warning: class `CppUnit?::SourceLine' for related function `CPPUNIT_SOURCELINE' is not documented.

this is the output of doxygen, as I guessed earlier. just disregard - cppunit has been installed correctly, and it will work OK

The next step libodbc++ & the 3th warning; checking sql.h usability... no checking sql.h presence... no checking for sql.h... no checking whether unixODBC should be used... no checking isql.h usability... no checking isql.h presence... no checking for isql.h... no configure: error: No ODBC driver manager configured. Pperhaps you need to give configure --with-odbc=/some/location? make: *** No rule to make target `install'. Stop. Installing the unixODBC driver manager only is not enough, sql.h is be part of unixODBC-devel, so i installed also the unixODBC-devel-rpm.

do you have unixODBC installed? please read the getting started document, at either https://www.campware.org/public_html/doc/gettingStarted.html or simply livesupport/doc/gettingStarted.html. it says, among other things: The LiveSupport development environment uses some system resources, that are not reasonable to include in the environment itself. One such resource is an ODBC datasource to a test database. This database has to be accessible for executing the test suites and applications within the LiveSupport development environment. First, LiveSupport expects a PostgreSQL database, and an ODBC Data Source accessible to it through unixODBC. Please refer to the documentation of these tools to set them up.

I have set it up with ODBCConnect and tested it with ODBC connection with open office "Accessing PostgreSQL Through OpenOffice?.org 1.1" by http://kandalaya.org/download/oo-pgsql.html It's working now, so i am happy - i am goning to the next step.

Some steps past, and now hxclient with error's - attach the logfile ERROR: UNIXCompile(datatype/common/vidrend) ERROR: Make failed. ERROR: UNIXCompile(datatype/rm/video/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/ram/renderer) ERROR: Make failed. ERROR: UNIXCompile(video/sitelib) ERROR: Make failed. ERROR: UNIXCompile(video/site) ERROR: Make failed. ERROR: UNIXCompile(datatype/h263/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/common/baserend) ERROR: Make failed. ERROR: UNIXCompile(datatype/smil/renderer/smil1) ERROR: Make failed. ERROR: UNIXCompile(datatype/smil/renderer/smil2) ERROR: Make failed. ERROR: UNIXCompile(datatype/smil/renderer/smil2/brush/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/smil/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/i420/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/image/jpg/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/image/gif/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/image/png/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/image/realpix/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/text/realtext/renderer) ERROR: Make failed. ERROR: UNIXCompile(datatype/mp4/video/renderer) ERROR: Make failed. ERROR: UNIXCompile(clientapps/simpleplayer) ERROR: Make failed. Build complete, 19 of 105 modules failed. cp: cannot stat `./release/splay': No such file or directory

thanks for the setup log. to be able to tell the exact details of why helix fails, we'd need the built.out file from the helix source directory, after the failed compilation. to get that file, please edit livesupport/tools/helix/hxclient_1_3_0_neptunex-2004-12-15/bin/in stall.sh so that it won't delete the tmp directory after attempting to compile and install. you can achieve this by simply commenting out the last line, e.g. at the end of install.sh, instead of: # clean up cd $basedir rm -rf tmp have: # clean up cd $basedir #rm -rf tmp then, please run livesupport/tools/helix/hxclient_1_3_0_neptu nex-2004-12-15/bin/install.sh, and after it finishes, post livesuppor t/tools/helix/hxclient_1_3_0_neptunex-2004-12-15/tmp/hxclient_1_3_0_ne ptunex-2004-12-15/build.out

It's to big, I have e-mail the build.out to Mantis

On this moment i think one pass further - gtk+ is be already installed with setting up the system yesterday. Do i need to install it again? Or is it really necessary to install it to the /livesupport directory again?

for the build.out - you could compress it by gzip or bzip2, as it's a text-only file, it should compress quite well. for gtk++ - yes, you need to compile it again.

You are right - attached the build out.

A stop with installing gtk+-2.4.13 from /livesupport/tools/gtk+/gtk+-2.4.13 to /livesupport/usr checking for jpeg_destroy_decompress in -ljpeg... yes checking for jpeglib.h... yes checking for jpeg_simple_progression in -ljpeg... yes checking for libpng12... no checking for png_read_info in -lpng... no configure: WARNING: *** PNG loader will not be built (PNG library not found) *** configure: WARNING: *** PNG loader will not be built (PNG header file not found) *** configure: error: *** Checks for PNG loader failed. You can build without it by passing *** --without-libpng to configure but many programs using GTK+ will *** not work properly. The PNG loader is also needed if you are compiling *** from CVS. make: *** No targets specified and no makefile found. Stop.

well, please install libpng (for redhat, I guess you'd need libpng- devel or something like that...)

You are right, the libpng devel of redhat (read fedora) had not been installed. An earlier problem - glib-mkenums were on traceable. Strangely because these had been installed with glib. I have edit my etc/profile and put the path of livesupport/bin and livesupport/usr/bin in to it. These two problems of libpng and gtk+ have been solved now.

Can i continue with the tools_setup or do i need for gtkmm, icu and curl components of hxclient? Do you have some news of the hxclient error's

How will curlpp be installed with setup? It's not in the makefile.

curlpp is not going to be installed, as it is not being used at the moment. this is the very reason it's not in the Makefile.

I've looked at the build.out you posted. some remarks to some of the errors: vidrend.cpp:200:27: X11/Intrinsic.h: No such file or directory vidrend.cpp:201:28: X11/StringDefs?.h: No such file or directory vidrend.cpp:202:23: X11/Shell.h: No such file or directory In file included from vidrend.cpp:217: ../../../common/include/hxevent.h:51:68: X11/keysymdef.h: No such file or directory it seems that you don't have the X11 (X server, either X.org or XFree86) development package installed. the above error message comes up several times. you get later: /usr/bin/ld: cannot find -lX11 for the same reason please try to compile the helix libraries again, with the X11 development packages installed...

This sounds ok - I have installed the xorg-sdk, the devel was be installed. The file's Intrinsic.h StringDefs?.h Shell.h & hxevent.h are locateble now No error anymore but stil a lot of warnings. I'll put only some down, but let me clear - my log file is be ending with "Build complete, 0 of 105 modules failed" Warning: Missing BIF source dep 'common_runtime' (include path ../../common/runtime/pub) Warning: Missing BIF dep 'common_system' (module library ../../common/system/rel/syslib.a) UMAKE Warning: removing duplicate source file="platform/unix/visuals.cpp" Warning: Missing BIF dep 'datatype_common_util' (module library ../../../../datatype/common/util/rel/dtutillib.a) Some warning message comes up several times. Wil a update of the source from be supporting us? Attached setup-hxclient2.log!

if it says 0 of 105 modules failed, all is OK. regarding the warnings, please contact the Helix Community site, at http://helixcommunity.org/ so to recap: all the tools that needed to be set up are successfully set up, right?

No not all of the tools - but i will go on with gtkmm, icu and curl now.

Ok done all the tools. But a error with core "make check" src/TimeConversionTest?.cxx: In member function `void LiveSupport::Core::TimeConversionTest?::ptimeToTmTest()': src/TimeConversionTest?.cxx:154: error: `ptime' is not a type make: *** [tmp/TimeConversionTest?.o] Error 1 Have i overlooked something? Of which component is this part?

I has used export path=~/bin:$PATH - read aclocal-1.7 version

no, this was our fault. please the a cvs update on the whole directory tree, and execute ./tools/libodbc++/libodbc++-0.2.3/bin/install.sh again (I had to patch libodbc++ so that gcc 3.4 will like it). then all the modules should compile and run the same as with gcc 3.3

Okay perhaps i am not most wanted .... but i have updated the cvs tree because I have already often done the tools i edit the main makefile like this; #setup: tools_setup doxytag_setup modules_setup products_setup setup: doxytag_setup modules_setup products_setup set export PATH=~/bin:$PATH end run ./tools/libodbc++/libodbc++-0.2.3/bin/install.sh make setup >& setup.log make compile >& compile.log but there is nothing in the bin directory of livesupport does here something go wrong? and i still have the question where i must start the programme. the log files are attached

Create my ln in var/www/html lrwxrwxrwx 1 root root 38 Jan 12 12:56 livesupportArchiveServer -> /livesupport/modules/archiveServer/var lrwxrwxrwx 1 root root 38 Jan 12 12:56 livesupportStorageServer -> /livesupport/modules/storageServer/var

The check file gives more insight. Perhaps i have problems in other components. I attached the check.log now

well, things compile don't get put in the livesupport/bin directory. for each module, in the modules directory, the result of the compilation is a library in modules/moduleName/lib. for 'product' (runnable applications), the result is in products/productName/tmp , like producst/scheduler/tmp/scheduler. you can invoke them through the Makefile in the product directory, for example to start the scheduler, use "make start" please note that livesupport is currently a project in development, the compiled results are now only in the build environment, we haven't done any packaging yet...

added all dependencies discovered during the resolution of this bug to livesupport/doc/developmentTools.html