Source: libxr
Version: 1.0-1
Severity: serious
Tags: squeeze sid
User: [email protected]
Usertags: qa-ftbfs-20100725 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[2]: Entering directory 
> `/build/user-libxr_1.0-1-amd64-8pPxnk/libxr-1.0/docs'
> SRCDIR=.. OUTDIR=. \
>       PROJECT="libxr" VERSION="1.0" \
>         doxygen ./Doxyfile
> warning: Tag `USE_WINDOWS_ENCODING' at line 11 of file ./Doxyfile has become 
> obsolete.
> To avoid this warning please update your configuration file using "doxygen -u"
> warning: Tag `DETAILS_AT_TOP' at line 23 of file ./Doxyfile has become 
> obsolete.
> To avoid this warning please update your configuration file using "doxygen -u"
> warning: Tag `MAX_DOT_GRAPH_WIDTH' at line 217 of file ./Doxyfile has become 
> obsolete.
> To avoid this warning please update your configuration file using "doxygen -u"
> warning: Tag `MAX_DOT_GRAPH_HEIGHT' at line 218 of file ./Doxyfile has become 
> obsolete.
> To avoid this warning please update your configuration file using "doxygen -u"
> warning: source ../tests/zblok is not a readable file or directory... 
> skipping.
> make[2]: *** [doxy] Segmentation fault
> make[2]: Leaving directory 
> `/build/user-libxr_1.0-1-amd64-8pPxnk/libxr-1.0/docs'
> make[1]: *** [override_dh_installdocs] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2010/07/25/libxr_1.0-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to