[Pkg-cryptsetup-devel] Compiler warnings in cryptsetup 1.0.3
Jonas Meurer
jonas at freesources.org
Thu Jun 8 23:31:43 UTC 2006
Hello,
tbm posted a list with packages which give compiler warnings in
their build logs recently to debian-devel. cryptsetup is one of them:
On 07/06/2006 Martin Michlmayr wrote to debian-devel at lists.debian.org:
> * Matthias Klose <doko at cs.tu-berlin.de> [2006-06-07 02:20]:
> > We did pick two compiler warnings and scanned the build logs of one
> > archive rebuild on alpha (64bit), where wrong code may be generated.
> > These warnings can be found in 1600 packages [4]; they are:
> > [4] http://people.debian.org/~tbm/logs/pointer/
>
> [...]
>
> Debian Cryptsetup Team
> cryptsetup 2:1.0.3-1
>
> [...]
the filtered compiler warnings are the following:
On 07/06/2006 Matthias Klose wrote to debian-devel-announce at lists.debian.org:
> - dereferencing type-punned pointer will break strict-aliasing rules
>
> For a description see the gcc(1) man page or [3]; a common
> workaround is to lower the optimization using -fno-strict-aliasing.
> See -Wstrict-aliasing and -Wstrict-aliasing=2 as well.
>
> - cast from pointer to integer of different size
> cast to pointer from integer of different size
>
> These warnings may point to code which is not 64bit clean. They are
> most likely not seen on 32bit architectures. See the amd64, alpha
> and ia64 build logs for these architecture specific warnings.
You can find the complete build log for cryptsetup at:
http://people.debian.org/~tbm/logs/pointer/long/cryptsetup_2:1.0.3-1_20060606-1313.bz2
And the particular compiler warnings:
http://people.debian.org/~tbm/logs/pointer/short/cryptsetup_2:1.0.3-1
my problem is, that the warning is generated while compiling gcrypt.c. I
cannot find gcrypt.c in the cryptsetup sources, and it's not even
available in any of the build-depends of cryptsetup. is this file
generated during the build process?
it would be great, if you could take a short look at it, maybe there is
really a problem related to 64bit architectures. and maybe the fix is
trivial.
...
jonas
More information about the Pkg-cryptsetup-devel
mailing list