Re: [Pkg-octave-devel] Compiling Octaviz in unstable
* Thomas Weber <thomas.weber.mail@gmail.com> [2005-12-08 15:26]:
> I have problems compiling Octaviz in unstable:
>
> $ apt-get source octaviz
> $ cd octaviz-0.4.0/
> $ dpkg-buildpackage -rfakeroot -us -uc
>
>
> This breaks with the following error (the last two lines are important):
> ======================================================================
> Building Utility vtkImageBlend.oct...
> In file included
> from /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c
> ++/4.0.3/backward/strstream:51,
> from /usr/include/vtk/vtkIOStream.h:32,
> from /usr/include/vtk/vtkSystemIncludes.h:40,
> from /usr/include/vtk/vtkIndent.h:24,
> from /usr/include/vtk/vtkObjectBase.h:43,
> from /usr/include/vtk/vtkCommand.h:47,
> from ../Common/octaviz.h:114,
> from ../Common/OctavizCommon.h:5,
> from vtkImageBlend.cc:3:
> /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c
> ++/4.0.3/backward/backward_warning.h:32:2: warning: #warning This file
> includes at least one deprecated or antiquated header. Please consider
> using one of the 32 headers found in section 17.4.1.2 of the C++
> standard. Examples include substituting the <X> header for the <X.h>
> header for C++ includes, or <iostream> instead of the deprecated header
> <iostream.h>. To disable this warning use -Wno-deprecated.
> vtkImageBlend.cc: In function ???bool FSvtkImageBlend_gnu_v3(const
> octave_shlib&)???:
> vtkImageBlend.cc:10: error: unknown escape sequence '\c'
> vtkImageBlend.cc:10: error: unknown escape sequence '\c'
> ======================================================================
>
> (As the file vtkImageBlend.cc is generated, I attach it for easier
> discussion). The problem seems to be some "\code" strings in the
> comment; however, these strings come from
> usr/include/vtk/vtkImageBlend.h
> and this file hasn't changed since the sarge release.
>
> Any ideas?
This comes probably from a change in g++ which became more stringent as
regards escape sequences in strings. At any rate, the "\code [...]
\endcode" blocks that appear in the *.h should be translated into
"@example [...] @end example" blocks in the DEFUN_DLD doc strings. I
think that the code in Wrapping/* must be changed in order to accomplish
this. What about contacting the upstream authors
(http://sourceforge.net/forum/forum.php?forum_id=348515)?
--
Rafael
Reply to: