TJ 2.4.3: Test Timezone

10 views
Skip to first unread message

Zerlett

unread,
Nov 20, 2010, 11:14:53 AM11/20/10
to TaskJuggler Users
Hi!

I tried to compile TaskJuggler 2.4.3 from source on an Gentoo/amd64
Linux machine (see below). However the test Timezone.tjp fails. The
docs did not say anything about what to do in that case. Suggestions
or experience with that anyone?

Thanks and best regards!

Zer

# tar xjf taskjuggler-2.4.3.tar.bz2
# cd taskjuggler-2.4.3/
# ./configure --without-arts --prefix=/usr/kde/3.5/
[...]
Good - your configure finished. Start make now
# make
[...]
make[2]: Entering directory `/usr/src/taskjuggler-2.4.3/TestSuite'
Testing in CSV-Reports
Testing in HTML-Reports
Testing in Misc
Testing in Scheduler
Testing in Syntax
Test Timezone.tjp failed!
Testing in TJX-Reports
1 errors detected!
make[2]: *** [all-local] Error 1
make[2]: Leaving directory `/usr/src/taskjuggler-2.4.3/TestSuite'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/taskjuggler-2.4.3'
make: *** [all] Error 2

Chris Schlaeger

unread,
Nov 20, 2010, 2:05:56 PM11/20/10
to taskjugg...@googlegroups.com
On Sat, Nov 20, 2010 at 5:14 PM, Zerlett <goo...@s.ek2.org> wrote:
> Test Timezone.tjp failed!
> Testing in TJX-Reports
> 1 errors detected!

That's probably the glibc bug that got fixed with more recent versions
again. The TJ2 git version has a workaround for this:

http://www.taskjuggler.org/cgi-bin/gitweb.cgi?p=taskjuggler.git;a=commitdiff;h=2382ed54f90c3c899badb3f56aaa2b3b5dba361e;hp=c666c5068312fec7db75e17d1c567d94127d1dda

Chris

Zerlett

unread,
Nov 20, 2010, 5:53:33 PM11/20/10
to TaskJuggler Users
Hi!

On 20 Nov., 20:05, Chris Schlaeger <cschlae...@gmail.com> wrote:
> That's probably the glibc bug that got fixed with more recent versions
> again. The TJ2 git version has a workaround for this:
> http://www.taskjuggler.org/cgi-bin/gitweb.cgi?p=taskjuggler.git;a=com...
Your guess was right, it does not occur with the git version :-)
...however apparently there is a "new" bug there:
# make
[...]
Making all in taskjuggler
make[2]: Entering directory `/usr/src/taskjuggler/taskjuggler'
/bin/sh ../libtool --silent --tag=CXX --mode=link g++ -o
taskjuggler main.o libtaskjuggler.la
g++: ./.libs/libtaskjuggler.so: No such file or directory
make[2]: *** [taskjuggler] Error 1
make[2]: Leaving directory `/usr/src/taskjuggler/taskjuggler'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/taskjuggler'
make: *** [all] Error 2

In taskjuggler/.libs there are two links
lrwxrwxrwx 1 root root 23 20. Nov 23:28 libtaskjuggler.so ->
libtaskjuggler.so.3.0.3
lrwxrwxrwx 1 root root 23 20. Nov 23:28 libtaskjuggler.so.3 ->
libtaskjuggler.so.3.0.3
but the link target, i.e. libtaskjuggler.so.3.0.3, does not exist.

Should I file a bug report for that or will this do?

Chris Schlaeger

unread,
Nov 21, 2010, 2:01:34 PM11/21/10
to taskjugg...@googlegroups.com
On Sat, Nov 20, 2010 at 11:53 PM, Zerlett <goo...@s.ek2.org> wrote:
> Hi!
>
> On 20 Nov., 20:05, Chris Schlaeger <cschlae...@gmail.com> wrote:
>> That's probably the glibc bug that got fixed with more recent versions
>> again. The TJ2 git version has a workaround for this:
>> http://www.taskjuggler.org/cgi-bin/gitweb.cgi?p=taskjuggler.git;a=com...
> Your guess was right, it does not occur with the git version :-)
> ...however apparently there is a "new" bug there:
> # make
> [...]
> Making all in taskjuggler
> make[2]: Entering directory `/usr/src/taskjuggler/taskjuggler'
> /bin/sh ../libtool --silent --tag=CXX --mode=link g++      -o
> taskjuggler  main.o libtaskjuggler.la
> g++: ./.libs/libtaskjuggler.so: No such file or directory

I'm afraid this is a libtool bug. I've been told that there is a
updated version of libtool that no longer has this problem.
Unfortunately, a lot of distros have picked up the broken version and
have not yet released an update.

Chris

Zerlett

unread,
Nov 21, 2010, 3:40:13 PM11/21/10
to TaskJuggler Users
On 21 Nov., 20:01, Chris Schlaeger <cschlae...@gmail.com> wrote:
> I'm afraid this is a libtool bug. I've been told that there is a
> updated version of libtool that no longer has this problem.
Oh dear :-(
But thanks for the info. I will wait for the next update of libtool
and file a bug if the problem persists ;-)
Reply all
Reply to author
Forward
0 new messages