Re: Fwd: GDCM

[Mathieu Malaterre <mathieu.malaterre@gmail.com>]

Ok I think I finally found what was the issue here. When building the
documentation with PDF:ON I had two: ADD_CUSTOM_TARGET. One for
creating the html documentation and one for creating the PDF. CMake
would then start doxygen once for the html target and once for the PDF
target, which would conflicts. In some case it would work and in very
rare occasion it would trigger a latex error (some input file not
ready yet).

In all cases I only have one single ADD_CUSTOM_TARGET (whether or not
PDF is ON).

Thanks dominique for report

On Wed, Apr 8, 2009 at 6:14 PM, Dominique Belhachemi
<domibel@cs.tu-berlin.de> wrote:
>
> The build process of the package is not thread-safe. I get the error only if
> i use the -j2 flag.
>
> Dominique
>
>
>
> On Wed, 8 Apr 2009, Mathieu Malaterre wrote:
>
>> Hi there,
>>
>>  Could anyone comment on the problem Dominique is having. I do not
>> understand the error message...
>>
>> Thanks.
>>
>> ---------- Forwarded message ----------
>> <snip>
>>
>> I tried to use your package on Lenny. i get following error message:
>>
>> #########################################################################
>> dpkg-source: info: building gdcm in gdcm_2.0.10-1.dsc
>>  debian/rules build
>> # quilt exits with 2 as return when there was nothing to do.
>> dh_testdir
>> # That's not an error here (but it's useful to break loops in crude
>> scripts)
>> /usr/bin/make -j2 -C
>> /home/domibel/lenny-backports/gdcm-2.0.10/debian/build-python2.4
>> QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a || test $?
>> = 2
>> make: ***
>> /home/domibel/lenny-backports/gdcm-2.0.10/debian/build-python2.4:
>> No such file or directory.  Stop.
>> make: *** [debian/build-python2.4-stamp] Error 2
>> make: *** Waiting for unfinished jobs....
>> No patches in series
>> touch debian/stamp-patched
>> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
>> debuild: fatal error at line 1319:
>> dpkg-buildpackage -rfakeroot -D -us -uc -j2 failed
>> #########################################################################
>>
>> I did not change your package.
>>
>>
>> After I got the error message I tried to change some lines to follow
>> the Python Policy (2.3).
>>
>> http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html
>>
>>
>> in debian/control
>> +XS-Python-Version: current
>>
>> in debian/rules
>> -PYVERS  := $(shell pyversions -vs)
>> +PYVERS  := $(shell pyversions -v -r debian/control)
>>
>> But this gave the same error. This time only with python2.5 instead of
>> python2.4 . Any idea what could be the reason for the problem?
>> ---------- End Forwarded message ----------
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-med-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>>
>



-- 
Mathieu