Bug 420803 – net-libs/libvncserver-0.9.9 USE=-crypt - ../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_*'

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Lukas Zavodny 2012-06-12 09:52:08 UTC]

....

  CC     LinuxVNC.o
  CC     VNConsole.o
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I..    -march=native -O2 -pipe -Wall   -c LinuxVNC.c
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I..    -march=native -O2 -pipe -Wall   -c VNConsole.c
  CC     example.o
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I..    -march=native -O2 -pipe -Wall   -c example.c
  CC     VNCommand.o
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I..    -march=native -O2 -pipe -Wall   -c VNCommand.c
VNCommand.c: In function 'main':
VNCommand.c:85:9: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result [-Wunused-result]
VNCommand.c:94:12: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result [-Wunused-result]
LinuxVNC.c: In function 'main':
LinuxVNC.c:155:12: warning: ignoring return value of 'fread', declared with attribute warn_unused_result [-Wunused-result]
  CCLD   linuxvnc
  CCLD   example
  CCLD   vncommand
mkdir: cannot create directory '.libs': File exists
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_read'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_get_algo_dlen'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_write'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_open'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_ctl'
collect2: ld returned 1 exit status
make[2]: *** [linuxvnc] Error 1
make[2]: *** Waiting for unfinished jobs....
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_read'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_get_algo_dlen'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_write'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_open'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_ctl'
collect2: ld returned 1 exit status
make[2]: *** [example] Error 1
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_read'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_get_algo_dlen'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_write'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_open'
../libvncserver/.libs/libvncserver.so: undefined reference to `gcry_md_ctl'
collect2: ld returned 1 exit status
make[2]: *** [vncommand] Error 1
make[2]: Leaving directory `/var/tmp/portage/net-libs/libvncserver-0.9.9/work/LibVNCServer-0.9.9/vncterm'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/net-libs/libvncserver-0.9.9/work/LibVNCServer-0.9.9'
make: *** [all] Error 2
 * ERROR: net-libs/libvncserver-0.9.9 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=net-libs/libvncserver-0.9.9'`,
 * the complete build log and the output of `emerge -pqv '=net-libs/libvncserver-0.9.9'`.
 * The complete build log is located at '/var/tmp/portage/net-libs/libvncserver-0.9.9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-libs/libvncserver-0.9.9/temp/environment'.
 * Working directory: '/var/tmp/portage/net-libs/libvncserver-0.9.9/work/LibVNCServer-0.9.9'
 * S: '/var/tmp/portage/net-libs/libvncserver-0.9.9/work/LibVNCServer-0.9.9'


Reproducible: Always

Steps to Reproduce:
1. emerge libvncserver-0.9.9

[Comment 1 Michael Weber (RETIRED) 2012-06-12 12:50:19 UTC]

Please provide `emerge --info`, `emerge -pv libvncserver` and the complete build.log, as mentioned on the bug reporting site.

[Comment 2 Lukas Zavodny 2012-06-14 10:02:21 UTC]

http://pastebin.com/LJiyBSJ2 emerge info
http://pastebin.com/MB65KwKt build log

emerge -pv libvncserver

[ebuild     U  ] net-libs/libvncserver-0.9.9 [0.9.8.2-r2] USE="gnutls jpeg threads zlib -crypt -ipv6 -no24bpp -test" 1,640 kB

[Comment 3 Jeroen Roovers (RETIRED) 2012-06-14 14:17:48 UTC]

(In reply to comment #2)
> http://pastebin.com/LJiyBSJ2 emerge info
> http://pastebin.com/MB65KwKt build log

Attach those, please.

[Comment 4 Jonathan Callen (RETIRED) 2012-06-17 19:05:15 UTC]

I just hit this same issue on my machine, and was able to trace it down to the --disable-gcrypt option passed to econf.  If USE=crypt is set, the package compiles sucessfully.

I will attach a failing compile log with EXTRA_ECONF=--disable-silent-rules (to ensure that the full command lines are shown).

[Comment 5 Jonathan Callen (RETIRED) 2012-06-17 19:07:27 UTC]

Created attachment 315621 [details]
build.log

[Comment 6 Jeroen Roovers (RETIRED) 2012-06-19 14:58:34 UTC]

USE=gnutls should make it DEPEND on dev-libs/libgcrypt, too, I guess.

[Comment 7 Mike Gilbert 2012-06-19 15:29:49 UTC]

Hmm... the gcrypt stuff is a bit hairy. There are two flags involved:

  --without-gcrypt        disable support for gcrypt
  --without-client-gcrypt disable support for gcrypt in libvncclient

Using --with-gnutls and --without-gcrypt together will cause under-linking of libvncserver.so.

While I'm poking at this, I want to look into that client-gcrypt flag to see if it is useful.

[Comment 8 Mike Gilbert 2012-06-19 16:22:33 UTC]

This should be fixed in 0.9.9. It probably needs to be addressed in 0.9.8.2-r2 as well.

+  19 Jun 2012; Mike Gilbert <[e-mail]> -libvncserver-0.9.8.2.ebuild,
+  libvncserver-0.9.9.ebuild, metadata.xml:
+  Force gcrypt when gnutls is selected, bug 420803. Add openssl dependency.
+  Rename crypt and no24bpp use flags to gcrypt and 24bpp.
+

[Comment 9 Mike Gilbert 2012-06-19 19:13:07 UTC]

0.9.8.2-r1 seems to be fine.