Comment 3 for bug 770870

Revision history for this message
Anton Gladky (gladky-anton) wrote : Re: [Bug 770870] Re: paraview version 3.8.1-2ubuntu3 failed to build on amd64 with GCC-4.6/oneiric

Hi, Julian,

the paraview 3.10 is almost ready for uploading to Debian Unstable. If
you want, you can try to build it for Ubuntu.
But it is _not_ in Debian yet.

http://anonscm.debian.org/gitweb/?p=debian-science/packages/paraview.git

Anton

On Mon, Jul 25, 2011 at 6:08 PM, Julian Taylor
<email address hidden> wrote:
> here is also a offsetof problem later in the build not covered by above patch.
> The patch in the debian bug solves this.
>
> But there is also another failure probably related to the libav transition:
> /tmp/buildd/paraview-3.8.1/VTK/IO/vtkFFMPEGWriter.cxx: In member function 'int vtkFFMPEGWriterInternal::Write(vtkImageData*)':
> /tmp/buildd/paraview-3.8.1/VTK/IO/vtkFFMPEGWriter.cxx:332:20: error: 'PKT_FLAG_KEY' was not declared in this scope
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/770870
>
> Title:
>  paraview version 3.8.1-2ubuntu3 failed to build on amd64 with
>  GCC-4.6/oneiric
>
> Status in “paraview” package in Ubuntu:
>  Confirmed
> Status in “paraview” source package in Oneiric:
>  Confirmed
> Status in “paraview” package in Debian:
>  Unknown
>
> Bug description:
>  paraview version 3.8.1-2ubuntu3 failed to build on amd64 with GCC-4.6/oneiric
>  Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2464424
>
>  Details about the rebuild:
>  https://lists.ubuntu.com/archives/ubuntu-devel/2011-April/033042.html
>
>  Direct link to the build log: https://launchpad.net/ubuntu/+archive
>  /test-rebuild-20110413/+buildjob/2464424/+files/buildlog_ubuntu-natty-
>  amd64.paraview_3.8.1-2ubuntu3_FAILEDTOBUILD.txt.gz
>
>  This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
>  Excerpt 2274 lines into the build log:
>
>  /build/buildd/paraview-3.8.1/VTK/Utilities/vtkmetaio/metaUtils.cxx:848:8: error: 'p' was not declared in this scope
>  /build/buildd/paraview-3.8.1/VTK/Utilities/vtkmetaio/metaUtils.cxx:854:11: error: 'p' was not declared in this scope
>  /build/buildd/paraview-3.8.1/VTK/Utilities/vtkmetaio/metaUtils.cxx:858:5: error: 'j' was not declared in this scope
>  /build/buildd/paraview-3.8.1/VTK/Utilities/vtkmetaio/metaUtils.cxx:859:11: error: 'p' was not declared in this scope
>  make[3]: *** [VTK/Utilities/vtkmetaio/CMakeFiles/vtkmetaio.dir/metaUtils.cxx.o] Error 1
>  make[3]: Leaving directory `/build/buildd/paraview-3.8.1/obj-x86_64-linux-gnu'
>  make[2]: *** [VTK/Utilities/vtkmetaio/CMakeFiles/vtkmetaio.dir/all] Error 2
>  make[2]: *** Waiting for unfinished jobs....
>  make[3]: Leaving directory `/build/buildd/paraview-3.8.1/obj-x86_64-linux-gnu'
>  [  2%] Built target vtkproj4
>  make[2]: Leaving directory `/build/buildd/paraview-3.8.1/obj-x86_64-linux-gnu'
>  make[1]: *** [all] Error 2
>  make[1]: Leaving directory `/build/buildd/paraview-3.8.1/obj-x86_64-linux-gnu'
>  make: *** [debian/stamp-makefile-build] Error 2
>  dpkg-buildpackage: error: debian/rules build gave error exit status 2
>  ******************************************************************************
>  Build finished at 20110425-1032
>  FAILED [dpkg-buildpackage died]
>  Purging chroot-autobuild/build/buildd/paraview-3.8.1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/paraview/+bug/770870/+subscriptions
>