File: libgpg-error-mingw-w64-dev.lintian-overrides

package info (click to toggle)
libgpg-error 1.35-1~bpo9+1
  • links: PTS, VCS
  • area: main
  • in suites: stretch-backports
  • size: 5,848 kB
  • sloc: ansic: 22,324; sh: 13,156; makefile: 488; awk: 333; lisp: 138; sed: 16
file content (22 lines) | stat: -rw-r--r-- 1,205 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
# libgpg-error-mingw-w64-dev is "arch-independent" from debian's perspective,
# since it ships binaries that are only used during cross-building
# windows software.
libgpg-error-mingw-w64-dev: arch-independent-package-contains-binary-or-object

# The location of these cross-building tools is the result of
# discussion with mingw maintainers:
# https://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/2016-February/003281.html
libgpg-error-mingw-w64-dev: file-in-unusual-dir
libgpg-error-mingw-w64-dev: non-standard-dir-in-usr

# DLLs exported via Samba need to be executable (see #796224)
libgpg-error-mingw-w64-dev: executable-not-elf-or-script

# the dependency_libs that are present in these win32 files are
# -lws2_32, which refers to /usr/i686-w64-mingw32/lib/libws2_32.a and
# /usr/x86_64-w64-mingw32/lib/libws2_32.a; this is necessary for
# building static Windows executables (like gpgv.exe), so i don't
# think it's an actual error to leave it in the distributed .la
# objects.
libgpg-error-mingw-w64-dev: non-empty-dependency_libs-in-la-file usr/i686-w64-mingw32/lib/libgpg-error.la
libgpg-error-mingw-w64-dev: non-empty-dependency_libs-in-la-file usr/x86_64-w64-mingw32/lib/libgpg-error.la