Re: testsuite development, any volunteer?

Hi,

On Thu, Jan 1, 2009 at 8:46 PM, Christian Thaeter <ct@...> wrote:
> Bhikkhu Mettavihari wrote:
>> Even with the below error I find
>> ./lumigui is working
>
> nice :) .. well ichthyo tried something with g_threads wich is obsolete
> now, i don't know if there are any artifact left from that, this should
> be cleared up. Thanks for starting working on this!
> Note: please respond your mails to the mailinglist
> (lumiera@...), not me in private. It is more
helpful if
> others see the reports too.

Shall do,

> About the AC_CONFIG_MACRO_DIR([m4]) i'll check that. Which linux
> distribution and what autotools version / gcc version do you use btw?

I am using this for testing
I am doing this on a laptop with 1 gb ram
Ubuntu 8.10
autoreconf (GNU Autoconf) 2.61
gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11)

>>> sync-waiting-test.cpp:(.text._ZN3lib4test16SyncWaiting_test3runERSt6vectorISsSaISsEE[lib::test::SyncWaiting_test::run(std::vector<std::basic_string<char,
>>> std::char_traits<char>, std::allocator<char> >,
>>> std::allocator<std::basic_string<char, std::char_traits<char>,
>>> std::allocator<char> > > >&)]+0x148): undefined reference to
>>> `g_thread_init'
>>> collect2: ld returned 1 exit status
>>> make[3]: *** [test-lib] Error 1
>>> make[3]: Leaving directory `/usr/local/src/LUMIERA/build'
>>> make[2]: *** [check-am] Error 2
>>> make[2]: Leaving directory `/usr/local/src/LUMIERA/build'
>>> make[1]: *** [check-recursive] Error 1
>>> make[1]: Leaving directory `/usr/local/src/LUMIERA/build'
>>> make: *** [check] Error 2
>>> root <at> dhammavihari:/usr/local/src/LUMIERA/build#

It would be nice to find out what that error is.

Mettavihari

>>> On Thu, Jan 1, 2009 at 8:19 PM, Bhikkhu Mettavihari
<tv.lists@...> wrote:
>>>> Hi Christian
>>>>
>>>> I have now gotten started
>>>> and like to give you a general progress report
>>>>
>>>> I installed nobug in /usr/local/src/nobug/
>>>> cd /usr/local/src/LUMIERA/
>>>> root <at> dhammavihari:/usr/local/src/LUMIERA# autoreconf -fi
>>>> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `scripts'.
>>>> libtoolize: copying file `scripts/config.guess'
>>>> libtoolize: copying file `scripts/config.sub'
>>>> libtoolize: copying file `scripts/install-sh'
>>>> libtoolize: copying file `scripts/ltmain.sh'
>>>> libtoolize: putting macros in `m4'.
>>>> libtoolize: copying file `m4/libtool.m4'
>>>> libtoolize: copying file `m4/ltoptions.m4'
>>>> libtoolize: copying file `m4/ltsugar.m4'
>>>> libtoolize: copying file `m4/ltversion.m4'
>>>> libtoolize: copying file `m4/lt~obsolete.m4'
>>>> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
>>>> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
>>>> root <at> dhammavihari:/usr/local/src/LUMIERA#
>>>>
>>>> I added
>>>> AC_CONFIG_MACRO_DIR([m4]) to the file configure.ac
>>>> and it worked.
>>>> I presume that is not to be reported ?
>>>>
>>>> I did not have boost 1.35 installed and that gave me errors like
>>>> checking boost/shared_ptr.hpp usability... no
>>>> checking boost/shared_ptr.hpp presence... no
>>>> checking for boost/shared_ptr.hpp... no
>>>> configure: error: boost::shared_ptr missing
>>>> (http://www.boost.org/)
>>>> root <at> dhammavihari:/usr/local/src/LUMIERA/build#
>>>> I also was missing a few other packages which I installed and the
>>>> configure file worked.
>>>>
>>>> Now the make is working and the make check is done
>>>> so now the fun starts 
>>>>
>>>> with metta
>>>> Mettavihari
>>>>
>>>> On Wed, Dec 31, 2008 at 6:00 AM, Christian Thaeter <ct@...> wrote:
>>>>> Bhikkhu Mettavihari wrote:
>>>>>> Hi Christian,
>>>>>>
>>>>>> I am running Linux on several machines
>>>>>> and run the old version of Cinelerra for all my production.
>>>>>> I would like to help, but please let me know what hard ware is required,
>>>>>> since my configurations might not be high enough.
>>>>> Should not be a problem, my guess is that a 1Ghz machine with 512MB ram
>>>>> would be useable to compile and run the testsuite with no problems.
>>>>> Actually I am quite interested that Lumiera scales down to smaller
>>>>> hardware as big ones (anyone on the list has a 8 or 16 core machine with
>>>>> 32+ GB ram and some TB diskspace and would volunteer in running some
>>>>> tests sometime in future? hey testing the lower end is cheap, but the
>>>>> upper end might become some challenge yet alone to find someone who has
>>>>> such hardware and makes it available for tests)
>>>>>
>>>>>> I have not gotten into even downloading your source
>>>>>> so please give me a few more down to earth hints on what to do.
>>>>> You need to install a lot of build tools and dependencies first, thats
>>>>> git, gcc, g++, NoBug, Gtkmm, gavl and many more (configure will fail and
>>>>> tell you whats missing). Most things execpt NoBug should be packaged for
>>>>> any decent distro, if not the configure tells you the homepage from
>>>>> where to get the things (but try to install the distros packages first)
>>>>>
>>>>> There is a Tutorial on:
>>>>>  http://www.pipapo.org/pipawiki/Lumiera/NewbiesTutorials
>>>>>
>>>>> If you find any inconsistencies in this tutorial you can right fix them
>>>>> in the wiki, or send a mail about your problems.
>>>>>
>>>>> When you gotten to the point the 'make check' succeeds with no errors
>>>>> then the fun starts:
>>>>>
>>>>> You go to the nobug dir and checkout the new test.sh from the
>>>>> development branch:
>>>>>  git checkout origin/devel -- tests/test.sh
>>>>>
>>>>> copy that test.sh into the lumiera tests dir, replacing the old one:
>>>>>  cp tests/test.sh /path/to/lumiera/tests/test.sh
>>>>>
>>>>> then you go back to lumiera build dir and 'make check' again. This will
>>>>> now report serveral failures. Looking at the ,testlog file gives a
>>>>> report. Then you edit the respective tests in lumiera/tests/*.tests most
>>>>> often some parenthesis ()[] and other regex chars have to be escaped \(
>>>>> \) \[ \] and so on. Other things may need fixing too or made more
>>>>> generic (this scales with your regex knowledge).
>>>>>
>>>>> After you did some fixes you 'make check' again and see if it worked. If
>>>>> yes, commit it and push it to the mob repository, then continue with the
>>>>> next failure. Voila, welcome to the Lumiera development world.
>>>>>
>>>>>        Christian
>>>>>
>>>>
>>>>
>>>> --
>>>> Streaming video from http://dharmavahini.tv
>>>>
>>>
>>>
>>> --
>>> Streaming video from http://dharmavahini.tv
>>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>
>

--

-- 
Streaming video from http://dharmavahini.tv