Re: [taskjuggler-users] problem compiling taskjuggler2

[Grégoire Barbier]

Hi Tomas,

I encountered a similar problem, which AFAIK occurs only with the master
TJ2 git branch and solved it with the attached patch (which I did not
yet published before this mail).
Actually the patch also address another compilation issue that you seems
not to have encountered and which AFAIK occurs only when compiling
without KDE/KDEPim support.

Regards.

--
Grégoire Barbier :: g à g76r.eu :: +33 6 21 35 73 49

Le 21/09/2011 03:55, Tomas a écrit :
> Hi, I'm getting an error when running make (configure is fine, got qt3
> and kde libs, alough I had to manually export QT_VERSION var, but
> anyway...)
>
> I run my configure with: --prefix=/usr/local/tj --with-kde-support=no
> --with-ical-support=no
>
> # make
> make all-recursive
> make[1]: Entering directory `/usr/local/TaskJuggler2'
> Making all in taskjuggler
> make[2]: Entering directory `/usr/local/TaskJuggler2/taskjuggler'
> /bin/sh ../libtool --silent --tag=CXX --mode=link g++ -Wno-long-
> long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -
> Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings
> -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-
> check-new -fno-common -o taskjuggler main.o libtaskjuggler.la
> ./.libs/libtaskjuggler.so: undefined reference to
> `SVGGanttTaskReport::SVGGanttTaskReport(Project*, QString const&,
> QString const&, int)'
> ./.libs/libtaskjuggler.so: undefined reference to
> `SVGTimeTimeReport::SVGTimeTimeReport(Project*, QString const&,
> QString const&, int)'
> collect2: ld returned 1 exit status
> make[2]: *** [taskjuggler] Error 1
> make[2]: Leaving directory `/usr/local/TaskJuggler2/taskjuggler'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/local/TaskJuggler2'
> make: *** [all] Error 2
>
> Many thanks for your help!
>

[Grégoire Barbier]

Le 21/09/2011 10:12, Grégoire Barbier a écrit :
> Actually the patch also address another compilation issue that you seems
> not to have encountered and which AFAIK occurs only when compiling
> without KDE/KDEPim support.

Well... I forgot to tell: this issue (that you seems not to encouter)
occurs only AFAIK when compiling without KDE/KDEPim support just after
the *very first* ./configure without these supports. If you first
compile with the support and then reconfigure without KDE support the
issue does not occurs (I suppose some .o or anything else remain between
configures).

However this is on TJ2 not TJ3 so most of these lists readers won't be
interested in this patch.