Your message dated Tue, 5 Jun 2012 01:33:24 +0000
with message-id <20120605013324.ga17...@scru.org>
and subject line Re: Bug#676005: zomg: FTBFS: ld: cannot find -lz
has caused the Debian Bug report #676005,
regarding zomg: FTBFS: ld: cannot find -lz
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 ow...@bugs.debian.org
immediately.)
--
676005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zomg
Version: 0.5.14-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120604 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> gcc -g -O2 -I/usr/include/libxml2 -g -O2 -lxml2 -lz -lm -o zomghelper-xspf
> zomghelper_xspf-zomghelper-xspf.o -lvorbisfile -lm
> /usr/bin/ld: cannot find -lz
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/04/zomg_0.5.14-2_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Mon, Jun 04, 2012 at 11:55:24PM +0200, Lucas Nussbaum wrote:
> > gcc -g -O2 -I/usr/include/libxml2 -g -O2 -lxml2 -lz -lm -o
> > zomghelper-xspf zomghelper_xspf-zomghelper-xspf.o -lvorbisfile -lm
> > /usr/bin/ld: cannot find -lz
This is #675682, fixed in libxml2 2.8.0+dfsg1-3.
--- End Message ---
