Bug 57193 refers to my intension to remove all gpgme apart from 0.3.14-r1 and 0.9.0-r1+. elmo currently has a couple of ebuild that refer to version 0.4.7. The good news is 0.9.0+ has the same api The better news it the fix to make these ebuilds work is: Replace the dependancy to refer to 0.9.0+ sed/patch configure.in the line: AC_CHECK_HEADER(gpgme.h and replace with: AC_CHECK_HEADER(gpgme/gpgme.h run autoconf and then proceed with the econf and following steps. The work in progress news is you need a option to enable/disable gpgme support with the use crypt flag. I.e gpgme could be installed and crypt flags could be disabled and this will still include the gpgme because it is there (rudely ingnoreing the use flags). The other items to fix list is that you install Makefile.* in /usr/share/doc... which is a bit weird. I may get round to do a patch for this however if you beat me to it I'd be more than gratefull.
1. The gpgme dependency is fixed in elmo 1.3.2. That should be enough, because I plan to remove older versions from the tree soon (1.3.2-r2 will be the first really good ebuild for elmo anyway). 2. The Makefiles got installed because upstream puts them in "doc/". I changed dodoc and only install relevant files now, thanks for pointing that out! 3. It seems like currently there's no option to disable gpgme when it's installed, but upstream promised me a patch for that. :) 4. When compiled with GCC 3.4, elmo immediately segfaults when started. I'd really like to wait for the upstream patch to reach me before letting 1.3.2-r2 out into the wild and removing the older versions. If it takes too long I'll stick in an ewarn and commit in anyway. Anything else I can do for you? :)
http://sourceforge.net/tracker/index.php?func=detail&aid=1034882&group_id=55793&atid=478284 patch. WANT_AUTOMAKE=1.8 automake -a -c WANT_AUTOCONF=2.5 autoconf myconf="${myconf} `use_with crypt gpgme`" following by configure etc... gcc-3.4 seemed to work for me ok. gcc-3.4 is a temparmental one though "Other requests?",hmm no I'm quite content. Although....
Thanks for the patch, working nicely. But I still have this segfault problem with gcc-3.4. Give me one or two more days to see if I can do anything about it, ok?
closing as it has been fixed. Elmo compiles and doesn't immediately segfault for me. You've included a warning anyway. Older version have been removed and I am very happy. Thank Michael/ Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r9 i686) ================================================================= System uname: 2.6.9-gentoo-r9 i686 AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Oct 24 2004, 08:06:09)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r5 sys-devel/automake: 1.8.5-r1 sys-devel/binutils: 2.15.90.0.1.1-r3 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r1
