Your message dated Tue, 17 Aug 2010 04:02:07 +0000
with message-id <e1oldnh-0003op...@franck.debian.org>
and subject line Bug#591417: fixed in ziproxy 3.1.3-1
has caused the Debian Bug report #591417,
regarding FTBFS on armel
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.)


-- 
591417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ziproxy
Version: 3.1.1-1
Severity: serious

Hi maintainer,

Your package fails to build from source on armel with the following error:
> arm-linux-gnueabi-gcc -DHAVE_CONFIG_H -I.     -g -O2 -MT cfgfile.o -MD -MP 
> -MF .deps/cfgfile.Tpo -c -o cfgfile.o cfgfile.c
> cfgfile.c: In function 'ReadCfgFile':
> cfgfile.c:738: internal compiler error: in choose_reload_regs, at 
> reload1.c:6456
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
> make[4]: *** [cfgfile.o] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> dh_auto_build: make -j1 returned exit code 2
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

The error appears like a bug in gcc when activating some optimisations
(or maybe '-g', I'm not sure). Ubuntu seems to have workarounded that
by disabling the optimisations. You might to check their patch. But,
indeed, a real fix would be better but maybe harder to get/work on.
The workaround allowws, at least, to build the package and get it in
the archive.

Regards,

-- 
Mehdi

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
Source: ziproxy
Source-Version: 3.1.3-1

We believe that the bug you reported is fixed in the latest version of
ziproxy, which is due to be installed in the Debian FTP archive:

ziproxy_3.1.3-1.debian.tar.gz
  to main/z/ziproxy/ziproxy_3.1.3-1.debian.tar.gz
ziproxy_3.1.3-1.dsc
  to main/z/ziproxy/ziproxy_3.1.3-1.dsc
ziproxy_3.1.3-1_amd64.deb
  to main/z/ziproxy/ziproxy_3.1.3-1_amd64.deb
ziproxy_3.1.3.orig.tar.bz2
  to main/z/ziproxy/ziproxy_3.1.3.orig.tar.bz2



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 591...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcos Talau <ta...@users.sourceforge.net> (supplier of updated ziproxy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 16 Aug 2010 20:22:32 -0300
Source: ziproxy
Binary: ziproxy
Architecture: source amd64
Version: 3.1.3-1
Distribution: unstable
Urgency: low
Maintainer: Marcos Talau <ta...@users.sourceforge.net>
Changed-By: Marcos Talau <ta...@users.sourceforge.net>
Description: 
 ziproxy    - compressing HTTP proxy server
Closes: 566589 591417
Changes: 
 ziproxy (3.1.3-1) unstable; urgency=low
 .
   * New upstream release (LP: #569611)
   * debian/patches/02_ziproxy_3.1.1_speedup.diff
     - Removed, merged upstream.
   * debian/preinst
     - Removed, old command moved to postinst (Closes: #566589)
       - Thanks piuparts ;-)
   * debian/control
     - Standards-Version updated
   * Disabled Nameservers option (Closes: #591417) (LP: #539874)
     - Thanks to all in 591417@ and the upstream!
     - debian/README.Debian
       - Reason for it added.
     - New patch: debian/02_off_nameservers_opt.diff
Checksums-Sha1: 
 040c49ff3629ed31bda52f7bc8e8459d92964d7c 1892 ziproxy_3.1.3-1.dsc
 3fb107e7de6be7e184475bffb5ba1a199349c147 261227 ziproxy_3.1.3.orig.tar.bz2
 6ace0eceb45eec826717ab1ce7c7bdd846b060de 8031 ziproxy_3.1.3-1.debian.tar.gz
 35ce44a8e3e6c9abbc4cf5698d94f6339da7ead7 130808 ziproxy_3.1.3-1_amd64.deb
Checksums-Sha256: 
 f450e2cbe2a1d58b882f2c0c4b55d708e00028e391785bbc8e7f971d2f6a0135 1892 
ziproxy_3.1.3-1.dsc
 d5cbb42de327c66c76b6332cb06ca294df8c5130481500c6e93788951211b7a2 261227 
ziproxy_3.1.3.orig.tar.bz2
 4823ce9c20437aea7aa60b1bf1b842516840ddd47131ee4bf55770b797f7e3ee 8031 
ziproxy_3.1.3-1.debian.tar.gz
 2b27d73e65857dffb5db86b96ae4c757763d6c474c9a0e7f638c6a337a8d4233 130808 
ziproxy_3.1.3-1_amd64.deb
Files: 
 d7ea01f412247068cd3e11805dcde188 1892 net extra ziproxy_3.1.3-1.dsc
 dd09206461dc9b11833ff2823943ac9f 261227 net extra ziproxy_3.1.3.orig.tar.bz2
 adfe654aa369a16ad0eacebbd0964b02 8031 net extra ziproxy_3.1.3-1.debian.tar.gz
 258de07d74314ece59e0b4f6b35a5d72 130808 net extra ziproxy_3.1.3-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJMagTjAAoJEDO+GgqMLtj/OvoQAL/up2cP9EUNuI3dlno7h6SO
AesPVwTbdCJ67bIIQYWNWZ4Oq3cGDusADkO9NwN+jJJrCJ7g6bqPTf+ADKoZoybJ
N9QYASudI59vc7NcUSWBnpVJVRTYRBQ7peblZERNhg3SKGcF2E+j5WVlbcTbUMOl
hgI3iAxuzI44bi/uiQDe7Vnk4S2K0zbXmMbmpUjHeQQuey+SWo6cStd0pwBR65/+
A+Z2t0KIPA1yJLbTHm8dji7611CsqI7NpIJJYdYbjLyKcWdkn0kvftY+io1/QmfQ
WPdQvmgemi3rwFcjYgnWN85++WKZz2yxRTfsWfD7YpnkwGFa7psVQvRhDoU2bxjr
Rd747xNF5SUOsfGhQGvJwoxnUWWZjNrbnCwLUIqhb9FRP95wnlsUWHsfP0S5XS8n
v6VckIUBNBTmLOXT8ltV8HsEgq+Vqb7Lcm8JSo3alok4yaA+SCogf6tF66OvRcXc
QUCGLTel4lErgc6fTx14XVM0r4pCaJKr0QfLXCK4C4ek2vnEKGinNcR7dIyZHJWo
iV/djBC4bGMuPKhhGSk5giRK9X9dvPxwBpo5ljyZYtIyx8C5znCK04wxSvfws7L6
aoMA0jI5erjObmgmF1DECqwabfdvg2+5NArF+Wvft7r7RaFTZRwN/vnjdsX05Yi8
EPwGiyvmQhQneVIuFizj
=dTeB
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to