Bugzilla Bug 66215

Compiling breaks with this message:

if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..      -O3 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -fforce-addr -fforce-mem-ffast-math -mpush-args -w -I/usr/include -Wall-Wcast-align -Wshadow -Wstrict-prototypes -MT engine-gpgsm.lo -MD -MP -MF ".deps/engine-gpgsm.Tpo" \
  -c -o engine-gpgsm.lo `test -f 'engine-gpgsm.c' || echo './'`engine-gpgsm.c; \
then mv -f ".deps/engine-gpgsm.Tpo" ".deps/engine-gpgsm.Plo"; \
else rm -f ".deps/engine-gpgsm.Tpo"; exit 1; \
fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -O3 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -fforce-addr -fforce-mem-ffast-math -mpush-args -w -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -MT engine-gpgsm.lo -MD -MP -MF .deps/engine-gpgsm.Tpo -c engine-gpgsm.c  -fPIC -DPIC -o .libs/engine-gpgsm.o
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -O3 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -fforce-addr -fforce-mem-ffast-math -mpush-args -w -I/usr/include -Wall -Wcast-align -Wshadow -Wstrict-prototypes -MT rungpg.lo -MD -MP -MF .deps/rungpg.Tpo -c rungpg.c  -fPIC -DPIC -o .libs/rungpg.o
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..      -O3 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -fforce-addr -fforce-mem-ffast-math -mpush-args -w -I/usr/include -Wall-Wcast-align -Wshadow -Wstrict-prototypes -MT posix-util.lo -MD -MP -MF ".deps/posix-util.Tpo" \
  -c -o posix-util.lo `test -f 'posix-util.c' || echo './'`posix-util.c; \
then mv -f ".deps/posix-util.Tpo" ".deps/posix-util.Plo"; \
else rm -f ".deps/posix-util.Tpo"; exit 1; \
fi
engine-gpgsm.c:41:20: assuan.h: No such file or directory
engine-gpgsm.c:59: error: parse error before "ASSUAN_CONTEXT"
engine-gpgsm.c:93: error: parse error before '}' token
engine-gpgsm.c: In function `close_notify_handler':
engine-gpgsm.c:126: error: dereferencing pointer to incomplete type

After emerging libassuan-0.6.6 everything is ok.

Reproducible: Always
Steps to Reproduce:

this is a duplicate of the 66190 bug.
it was already fixed.

*** This bug has been marked as a duplicate of 66190 ***