Bug 325991 – net-analyzer/openvas-libraries-3.1.0.rc2 (et al) cannot find gpgme.h

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Rick Farina (Zero_Chaos) 2010-06-28 14:53:05 UTC]

When building openvas-libraries (an application which needs gpgme.h) it fails.

For some reason I noticed in gentoo that gpgme.h isn't in /usr/include it is in /usr/include/gpgme

This isn't standard for sure and since I can't find any other apps that ship /usr/include/gpgme.h this doesn't seem to make sense to me.

I am guessing this should be assigned to the gpgme maintainer but I defer to the wisdom of the bug wranglers.

Reproducible: Always

Steps to Reproduce:
1.Try to build openvas-libraries-3.1.0.rc
2.cannot find /usr/include/gpgme.h
3.cry

Actual Results:  
Can't find /usr/include/gpgme.h

Expected Results:  
/usr/include/gpgme/gpgme.h should reside in /usr/include/gpgme.h

[Comment 1 Rafał Mużyło 2010-06-28 17:04:57 UTC]

'gpgme-config --cflags' outputs '-I/usr/include/gpgme'
How about attaching the build log of that application ?

[Comment 2 Rick Farina (Zero_Chaos) 2010-06-28 18:02:54 UTC]

Created attachment 236835 [details]
build.log

Please note, this ebuild is not in portage, this is something I'm working on.

[Comment 3 Rick Farina (Zero_Chaos) 2010-06-28 18:03:40 UTC]

Created attachment 236837 [details]
ebuild

current ebuild if anyone wants to see it for some reason

[Comment 4 Rafał Mużyło 2010-06-28 23:30:15 UTC]

The log seems to be from a completely different ebuild
and makes no sense at all - it runs both configure script
and cmake.

[Comment 5 Rick Farina (Zero_Chaos) 2010-06-29 02:00:11 UTC]

(In reply to comment #4)
> The log seems to be from a completely different ebuild
> and makes no sense at all - it runs both configure script
> and cmake.
> 

While I appreciate your confusion, and I agree it is odd, that is tough luck.  It is what it is. This is the correct ebuild. As I pasted it you are more than welcome to try it out.

[Comment 6 Rafał Mużyło 2010-06-29 12:36:20 UTC]

Next time, be more clear was your bug is about.
It seems it's about two things:
- a few months ago, openvas 3.0 was released (that's a dupe of bug 298307)
- openvas upstream fails at proper use of any given
build system (their configure.in was quite a bit Frankensteinish,
for 3.1 (to be released) they've switched to cmake and didn't do much better)

It seems, that unless they fix it before 3.1 gets released, the ebuild will
need to do a lot of hacking. The problem with gpgme (they fail to use 
gpgme-config in cmake) will be just a tip of the iceberg.

[Comment 7 Rick Farina (Zero_Chaos) 2010-07-14 22:54:52 UTC]

Upstream has fixed this in 3.1.0.rc3

Please close this bug.

[Comment 8 Rick Farina (Zero_Chaos) 2010-07-14 22:55:56 UTC]

Created attachment 238775 [details]
version bump to fix issue

[Comment 9 Hanno Böck 2011-10-09 17:37:56 UTC]

we never had openvas 3 in the tree.