[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#650217: istgt: ftbfs on squeeze



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Michal,

On 27.11.2011 21:52, Michal Suchanek wrote:
> /bin/sh: -c: line 3: syntax error near unexpected token `('
> /bin/sh: -c: line 3: `  Usage: dpkg-buildflags [<action>]  Actions:   --get <flag>       output the requested flag to stdout.   --origin <flag>    output the origin of the flag to stdout:                      value is one of vendor, system, user, env.   --list             output a list of the flags supported by the current vendor.   --export=(sh|make) output commands to be executed in shell or make that export                      all the compilation flags as environment variables.   --help             show this help message.   --version          show the version.'
> make[1]: *** [override_dh_auto_configure] Error 1
> make[1]: Leaving directory `/usr/src/istgt-0.4~20111008'
> make: *** [build] Error 2

yes, istgt has a dependency to dpkg 1.16.1 available from Wheezy and
beyond. Since dpkg is an essential package and this particular version
is guaranteed to be fulfilled in Wheezy, I didn't add a build-dependency
to it.

As far as I know, there is no backport of Squeeze for dpkg available
yet. Hence it is not easily possible to fix that bug cleanly. If you
want to make a backport of istgt for Squeeze for your own purposes, just
remove the line "$(shell dpkg-buildflags --export=configure)" entirely.
You will lose build-hardening flags by doing so though, introduced by
dpkg 1.16.1 as well, but you can at least compile istgt. That said, I
have never tried whether that actually works.

- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJO0tZnAAoJEMcrUe6dgPNt8J4P/iLuYNdA/gDlgbSWceYfLn4a
RiS7C4BCcUUT+ixDEpRyza8crlj6fJVbTrDC7TUm0huGJ52yW/2E9PXnh4sCy6SE
zs4SwiqG3YKLHXDqA7DsuWJLcWgSg728G3h5M/0I3dVNJgLxEgSFDKRLZyyd2DBY
W4typKX5sgL3bCeqfQw52MSSCeSVqPUr1p0rahUT+DzEifuWAEpktJJY5wHkbNGo
PqLSd6WSNvvUnnvkKJLed9U+PhhEhl6IIXD2phvrHoCGU2IRylvuDUJyGyq8Z+O6
bY+wS1cvHRe6nuXlPELRj6/90XU0Iw2bKdRJai3ZT/iEQ+lVbAGduUHJ1mZcDbIn
ISkcFfZcD47bxJdjd1uYo2s2dSjLpVWJBwaShvn1LbKX4zF1u26ojrQf+6ISVcOx
bTH9UB3i5BvgKn5IO7ualnZtd4ZNT0j4/tICs22IECIN4K6vs1ytFRzT7hQs0mEg
r4O9dK5ZB72otZPivD4X7dSRvU8N3LC4KfgpKLBglqeHUEy8ftPijOms4tszkGYR
0oqjc398MiPD9HeYCz1XF7RuCduYXENtibfX4MWCWPigb244GS0b/UD2GkuIizsy
2rG7U50TxAE7g8DPezkiE6fMJ6FXT7y5YXy9erE2NafqfZkjITc7yrGnecGK1tWU
PFlZg60zUJs/d3Wmn5Z/
=XyW0
-----END PGP SIGNATURE-----



Reply to: