Bug 635770

Summary:	app-crypt/libu2f-server-1.0.1 : /.../openssl.c:36:27: fatal error: openssl/ecdsa.h: No such file or directory
Product:	Gentoo Linux	Reporter:	Toralf Förster <toralf>
Component:	Current packages	Assignee:	Göktürk Yüksek <gokturk>
Status:	RESOLVED OBSOLETE
Severity:	normal	Keywords:	TESTFAILURE
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge-info.txt app-crypt:libu2f-server-1.0.1:20171029-085919.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2

Description Toralf Förster gentoo-dev

2017-10-29 10:59:24 UTC

libtool: compile:  x86_64-pc-linux-gnu-gcc -DPACKAGE_NAME=\"libu2f-server\" -DPACKAGE_TARNAME=\"libu2f-server\" -DPACKAGE_VERSION=\"1.0.1\" "-DPACKAGE_STRING=\"libu2f-server 1.0.1\"" -DPACKAGE_BUGREPORT=\"yubico-devel@googlegroups.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"libu2f-server\" -DVERSION=\"1.0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_JSON_OBJECT_OBJECT_GET_EX=1 -I. -I/var/tmp/portage/app-crypt/libu2f-server-1.0.1/work/libu2f-server-1.0.1/u2f-server -I/var/tmp/portage/app-crypt/libu2f-server-1.0.1/work/libu2f-server-1.0.1/u2f-server/.. -I./.. -I/usr/include/json-c -O2 -pipe -march=native -Wall -c /var/tmp/portage/app-crypt/libu2f-server-1.0.1/work/libu2f-server-1.0.1/u2f-server/openssl.c  -fPIC -DPIC -o .libs/openssl.o
/var/tmp/portage/app-crypt/libu2f-server-1.0.1/work/libu2f-server-1.0.1/u2f-server/openssl.c:36:27: fatal error: openssl/ecdsa.h: No such file or directory
 #include <openssl/ecdsa.h>
                           ^
compilation terminated.

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 13.0-desktop_test_20171027-180434

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-6.4.0 *

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python3.6 (fallback)
  [3]   python2.7 (fallback)




emerge -qpv app-crypt/libu2f-server
[ebuild  N    ] app-crypt/libu2f-server-1.0.1  USE="{test} -libressl -static-libs" ABI_X86="(64) -32 (-x32)"

Comment 1 Toralf Förster gentoo-dev

2017-10-29 10:59:27 UTC

Created attachment 500740 [details]
emerge-info.txt

Comment 2 Toralf Förster gentoo-dev

2017-10-29 10:59:30 UTC

Created attachment 500742 [details]
app-crypt:libu2f-server-1.0.1:20171029-085919.log

Comment 3 Toralf Förster gentoo-dev

2017-10-29 10:59:33 UTC

Created attachment 500744 [details]
emerge-history.txt

Comment 4 Toralf Förster gentoo-dev

2017-10-29 10:59:36 UTC

Created attachment 500746 [details]
environment

Comment 5 Toralf Förster gentoo-dev

2017-10-29 10:59:39 UTC

Created attachment 500748 [details]
etc.portage.tbz2

Comment 6 Toralf Förster gentoo-dev

2017-10-29 10:59:42 UTC

Created attachment 500750 [details]
logs.tbz2

Comment 7 Toralf Förster gentoo-dev

2017-10-29 10:59:45 UTC

Created attachment 500752 [details]
temp.tbz2

Comment 8 Göktürk Yüksek archtester

2019-06-05 19:36:18 UTC

I'm not sure why your tinderbox doesn't have openssl/ecdsa.h. I don't see a USE flag that controls its installation either. Is it possible to run this with libu2f-server-1.1.0 and see if we can reproduce?

Comment 9 Toralf Förster gentoo-dev

2019-06-05 19:58:42 UTC

(In reply to Göktürk Yüksek from comment #8)
> I'm not sure why your tinderbox doesn't have openssl/ecdsa.h. I don't see a
> USE flag that controls its installation either. Is it possible to run this
> with libu2f-server-1.1.0 and see if we can reproduce?

bhat bug report is 2 years old, so - but app-crypt/libu2f-server-1.1.0 is fine here so far

Comment 10 Göktürk Yüksek archtester

2019-06-05 20:42:45 UTC

Let's not worry about it if we cannot reproduce.