Bug#697805: marked as done (Package gcc-4.7 fails to build with dpkg-buildpackage)
Your message dated Wed, 09 Jan 2013 22:39:09 +0100
with message-id <50EDE37D.2040204@debian.org>
and subject line Re: Bug#697805: Package gcc-4.7 fails to build with dpkg-buildpackage
has caused the Debian Bug report #697805,
regarding Package gcc-4.7 fails to build with dpkg-buildpackage
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
697805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697805
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.7
Version: 4.7.2-4
Severity: serious
Justification: fails to build from source (using dpkg-buildpackage)
I obtained the gcc 4.7 sources via `apt-get source gcc-4.7'. I then tried
debuild on the newly created directory (gcc-4.7-4.7.2), when it failed, I tried
using dpkg-buildpackage directly. It also fails, with the same error, when
applying the debian specific patches. The salient part of the output follows.
Applying patch gcc-default-format-security.diff
patching file src/gcc/c-family/c-common.c
Hunk #1 succeeded at 202 (offset 1 line).
patching file src/gcc/c-family/c.opt
Hunk #1 succeeded at 392 (offset 8 lines).
patching file src/gcc/doc/invoke.texi
Hunk #1 FAILED at 3102.
Hunk #2 FAILED at 3155.
2 out of 2 hunks FAILED -- rejects in file src/gcc/doc/invoke.texi
Patch gcc-default-format-security.diff does not apply (enforce with -f)
make: *** [stamps/02-patch-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1357:
dpkg-buildpackage -rfakeroot -D -us -uc failed
This is because the gcc documentation has been moved to non-free but the debian
scripts have not been updated to match. The contents of src/gcc/doc/invoke.texi
are a message indicating the documentation has been removed. Modifying the
downloaded source so it again contains the documentation allows it to build.
I believe the solution is to edit the failing patch file so that it does not try to
patch anything in the doc directory.
The same problem also seems to apply to gcc 4.6 and gcc 4.5.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gcc-4.7 depends on:
ii binutils 2.22-7.1
ii cpp-4.7 4.7.2-4
ii gcc-4.7-base 4.7.2-4
ii libc6 2.13-37
ii libgcc1 1:4.7.2-4
ii libgmp10 2:5.0.5+dfsg-2
ii libgomp1 4.7.2-4
ii libitm1 4.7.2-4
ii libmpc2 0.9-4
ii libmpfr4 3.1.0-5
ii libquadmath0 4.7.2-4
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages gcc-4.7 recommends:
ii libc6-dev 2.13-37
Versions of packages gcc-4.7 suggests:
pn binutils-gold <none>
pn gcc-4.7-doc <none>
pn gcc-4.7-locales <none>
ii gcc-4.7-multilib 4.7.2-4
pn libgcc1-dbg <none>
pn libgomp1-dbg <none>
pn libitm1-dbg <none>
pn libmudflap0-4.7-dev <none>
pn libmudflap0-dbg <none>
pn libquadmath0-dbg <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 09.01.2013 21:48, schrieb Logan Perkins:
> Package: gcc-4.7
> Version: 4.7.2-4
> Severity: serious
> Justification: fails to build from source (using dpkg-buildpackage)
>
>
>
>
> I obtained the gcc 4.7 sources via `apt-get source gcc-4.7'. I then tried
> debuild on the newly created directory (gcc-4.7-4.7.2), when it failed, I tried
> using dpkg-buildpackage directly. It also fails, with the same error, when
> applying the debian specific patches. The salient part of the output follows.
closing as invalid. The package builds ok on any Debian system. Please recheck
with a freshly created sid chroot.
--- End Message ---
Reply to: