Bug 277890 – [TRACKER] app-crypt/gpgme-1.2.0 induced bugs

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Andrew Savchenko 2009-07-15 06:10:06 UTC]

This is for bugs induced by gpgme-1.2.0.
Currently I got a lot of pain with LFS support on x86.

[Comment 1 Wolfram Schlich (RETIRED) 2011-08-01 07:42:19 UTC]

Andrew said:
"gpgme-1.2.0 requires all client programs to define LFS support in the same way
as it does itself, thus gpgme fails without -D_FILE_OFFSET_BITS=64 on x86."

Is this still true for gpgme-1.3.x?

I need to fix bug #362239 which was created during fixing the gpgme issue described in bug #277888 ...

[Comment 2 Andrew Savchenko 2011-08-01 13:30:51 UTC]

(In reply to comment #1)
> Andrew said:
> "gpgme-1.2.0 requires all client programs to define LFS support in the same way
> as it does itself, thus gpgme fails without -D_FILE_OFFSET_BITS=64 on x86."
> 
> Is this still true for gpgme-1.3.x?

Yes. This is the library requirement, you can read section 2.3 Large File Support of the gpgme info file for further details.

"GPGME is compiled using largefile support by default.  This means
that your application must do the same, at least as far as it is
relevant for using the `gpgme.h' header file.  All types in this header
files refer to their largefile counterparts, if they are different from
any default types on the system."

[Comment 3 Wolfram Schlich (RETIRED) 2011-08-01 13:47:48 UTC]

Thanks Andrew. What do you think about bug #362239?

[Comment 4 Andrew Savchenko 2011-08-01 17:06:38 UTC]

(In reply to comment #3)
> Thanks Andrew. What do you think about bug #362239?

You haven't posted your build log, I can say almost nothing.
Based on what you have wrote in that bug, I see two possibilities:
1) Force LFS support for mcabber in some other way.
2) Fix plugin build instead.

[Comment 5 Dane Smith (RETIRED) 2012-11-05 15:32:42 UTC]

All depend bugs are closed.

Closing this for now. If there are still issues, please re-open it.