[forwarded from http://bugs.debian.org/513420]
Reverting the fix for PR38615 on the 4.3 branch lets the build succeed.
What am I trying to do:
* Build libgsf from source again on amd64 (or build libgsf svn trunk).
How am I trying to do it / steps to reproduce:
* Set up a sid environment in which to build libgsf from the Debian source
package, e.g. in pbuilder.
* Get the libgsf source package and extract it.
* In the source directory, run
env MALLOC_CHECK_=2 debian/rules build
What behaviour did I expect to get:
* The libgsf build runs to completion.
What behaviour did I actually get:
* The libgsf build fails during documentation generation, with messages
similar to the following:
creating gsf-scan
gtk-doc: Running scanner gsf-scan
sh: line 1: 27898 Segmentation fault ( ./gsf-scan )
Scan failed:
make[3]: *** [scan-build.stamp] Error 139
make[3]: Leaving directory `/tmp/buildd/libgsf-1.14.11/build/doc'
* This behaviour is fully repeatable for me.
Notes and observations:
* "gsf-scan" is built from generated sources using gtk-doc-tools.
* To preserve the gsf-scan sources and objects, comment out the unlink line
which removes them in /usr/bin/gtkdoc-scangobj .
* When running plain "debian/rules build" without the env MALLOC_CHECK_=2,
the problem manifests at a later point in the build as follows:
cd ../../doc/html && gtkdoc-mkhtml gsf ../gsf-docs.sgml
../xml/text.xml:255: parser error : Input is not proper UTF-8, indicate
encoding !
Bytes: 0xD0 0x45 0x2E 0x02
When to quote fields.Default value: ÐE.
^
../xml/text.xml:255: parser error : PCDATA invalid Char value 2
When to quote fields.Default value: ÐE.
^
../xml/text.xml:279: parser error : chunk is not well balanced
^
../gsf-docs.sgml:232: parser error : Failure to process entity GsfText
&GsfText;
^
../gsf-docs.sgml:232: parser error : Entity 'GsfText' not defined
&GsfText;
^
unable to parse ../gsf-docs.sgml
make[3]: *** [html-build.stamp] Error 6
This can be tracked back to a garbage string in the block within
the block for GsfOutputCsvQuotingMode in doc/gsf.args which is a
file generated by gsf-scan. The garbage string can vary between repeated
attempts.
* This libgsf version (1.14.11-1) has previously been built successfully on
all architectures.
* The problem is still reproducible for me when the optimisation level is
reduced (in debian/rules) to -O1 .
* I could not reproduce the problem in the following variations:
* When lowering the optimisation level to -O0 .
* Building in a 32-bit pbuilder chroot on amd64.
* Building in a sid environment with the gcc-4.3 packages downgraded to
the 4.3.2-1.1 versions from testing.
* Building using CC=gcc-4.2 .
* Building using CC=gcc-4.1 .
* Building using CC=/usr/lib/gcc-snapshot/bin/gcc .
which makes me suspect that the problem isn't with the (generated)
gsf-scan sources, but with gcc's code generation.
--
Summary: [4.3 regression] wrong code building libgsf
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: doko at ubuntu dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39015