Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-22 Thread Andreas Metzler
On 2016-02-22 Daniel Kahn Gillmor wrote: > On Sun 2016-02-21 05:12:49 -0800, Andreas Metzler wrote: > > I have now merged/selectively pulled the necessary changes on the > > experimental branch. Builds-for-me. Could you take a look? [...] > hm, nope, i'm actually seeing an

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-21 Thread Daniel Kahn Gillmor
On Sun 2016-02-21 05:12:49 -0800, Andreas Metzler wrote: > I have now merged/selectively pulled the necessary changes on the > experimental branch. Builds-for-me. Could you take a look? hm, nope, i'm actually seeing an error on the experimental branch with the texlive compilation: - [72]

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-21 Thread Daniel Kahn Gillmor
On Sun 2016-02-21 00:44:11 -0800, Andreas Metzler wrote: > Why don't we simply hardcode this as 1, 2 or 42 instead? Having changing > builds without source changes (just becuse the lenght of > debian/changelog increased) seems wrong to me. You're welcome to do this however you you think best, of

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-21 Thread Andreas Metzler
On 2016-02-21 Andreas Metzler wrote: > On 2016-02-20 Daniel Kahn Gillmor wrote: > [...] >> - m4_esyscmd([git rev-parse --short HEAD | tr -d '\n\r'])) >> + m4_esyscmd([printf %x $(wc -l < debian/changelog)])) > [...] > Why don't we

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-21 Thread Andreas Metzler
On 2016-02-20 Daniel Kahn Gillmor wrote: [...] > Ugh, it looks like it builds when building from git, but not from a > tarball. This is because we're using autoreconf and upstream's > configure.ac relies on being in a git repo (it selects the revision > number from the

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-20 Thread Daniel Kahn Gillmor
Hi Andreas-- On Fri 2016-02-19 12:59:21 -0500, Andreas Metzler wrote: > On 2016-02-17 Daniel Kahn Gillmor wrote: > [...] >> The attached set of patches against branch1.6 (also in the >> debian-windows branch of >> https://anonscm.debian.org/git/users/dkg/libgcrypt.git)

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-19 Thread Andreas Metzler
On 2016-02-17 Daniel Kahn Gillmor wrote: [...] > The attached set of patches against branch1.6 (also in the > debian-windows branch of > https://anonscm.debian.org/git/users/dkg/libgcrypt.git) provides this > for libgcrypt. [...] Hello, this does not build for me on

Bug#814954: libgcrypt20: add libgcrypt-mingw-w64-dev for cross-building to Windows targets

2016-02-16 Thread Daniel Kahn Gillmor
Package: libgcrypt20 Version: 1.6.4-5 Severity: normal Tags: patch We should be able to build Windows executables from debian, including GnuPG (for gpgv-win32 for win32-loader). Having a cross-building toolchain will make that possible. The attached set of patches against branch1.6 (also in the