Re: GnuPG 2.0.22 compiling on Mac OS X fails

2013-10-06 Thread Michael

Am 05.10.2013 um 17:08 schrieb Werner Koch w...@gnupg.org:

 On Sat,  5 Oct 2013 14:58, so...@dersonic.org said:
 
 i just tried to compile the 2.0.22 version on Mac OS X 10.8.5 with XCode 5.0.
 
 This is known.  See for example bug 1541.  Sorry, I can't do anything
 about it until someone provides a tested solution.

I tryed the workaround described in the bug report.
But i use gl/stdint.h instead of sm/stdint.h.

The workaround works well so far.

# include 
///Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/5.0/include/stdint.h

typedef longintptr_t;
typedef long long   intmax_t;
typedef unsigned long   uintptr_t;
typedef unsigned long long  uintmax_t;





smime.p7s
Description: S/MIME cryptographic signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


GnuPG 2.0.22 compiling on Mac OS X fails

2013-10-05 Thread Michael
Hi,

i just tried to compile the 2.0.22 version on Mac OS X 10.8.5 with XCode 5.0.

But it fails :

#pragma weak pth_waitpid
 ^
exechelp.c:68:14: warning: weak identifier 'pth_fork' never declared
#pragma weak pth_fork
 ^

signal.c:125:41: warning: adding 'int' to a string does not append to the string
  [-Wstring-plus-int]
  write (2, 0123456789+(value/i), 1);
^~
signal.c:125:41: note: use array indexing to silence this warning
  write (2, 0123456789+(value/i), 1);
^
   [ ]

///Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/5.0/include/stdint.h:32:36:
 warning: 
  #include_next with absolute path
defined(__has_include_next)  __has_include_next(stdint.h)
   ^
///Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/5.0/include/stdint.h:33:3:
 warning: 
  #include_next with absolute path
# include_next stdint.h
  ^
In file included from estream-printf.c:54:
In file included from ../gl/stdint.h:66:
/usr/include/inttypes.h:238:10: error: unknown type name 'intmax_t'
  extern intmax_t imaxabs(intmax_t j);
 ^
/usr/include/inttypes.h:238:27: error: unknown type name 'intmax_t'
  extern intmax_t imaxabs(intmax_t j);
  ^
/usr/include/inttypes.h:242:9: error: unknown type name 'intmax_t'
intmax_t quot;
^
/usr/include/inttypes.h:243:9: error: unknown type name 'intmax_t'
intmax_t rem;
^
/usr/include/inttypes.h:246:28: error: unknown type name 'intmax_t'
  extern imaxdiv_t imaxdiv(intmax_t numer, intmax_t denom);
   ^
/usr/include/inttypes.h:246:44: error: unknown type name 'intmax_t'
  extern imaxdiv_t imaxdiv(intmax_t numer, intmax_t denom);
   ^
/usr/include/inttypes.h:249:10: error: unknown type name 'intmax_t'
  extern intmax_t strtoimax(const char * restrict nptr, char ** restric...
 ^
/usr/include/inttypes.h:250:10: error: unknown type name 'uintmax_t'; did you
  mean 'uintptr_t'?
  extern uintmax_t strtoumax(const char * restrict nptr, char ** restric...
 ^
/usr/include/i386/types.h:109:24: note: 'uintptr_t' declared here
typedef unsigned long   uintptr_t;
^
In file included from estream-printf.c:54:
In file included from ../gl/stdint.h:66:
/usr/include/inttypes.h:260:10: error: unknown type name 'intmax_t'
  extern intmax_t wcstoimax(const wchar_t * restrict nptr, wchar_t ** re...
 ^
/usr/include/inttypes.h:261:10: error: unknown type name 'uintmax_t'; did you
  mean 'uintptr_t'?
  extern uintmax_t wcstoumax(const wchar_t * restrict nptr, wchar_t ** r...
 ^
/usr/include/i386/types.h:109:24: note: 'uintptr_t' declared here
typedef unsigned long   uintptr_t;
^


Best regards,

Michael

smime.p7s
Description: S/MIME cryptographic signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: GnuPG 2.0.22 compiling on Mac OS X fails

2013-10-05 Thread Werner Koch
On Sat,  5 Oct 2013 14:58, so...@dersonic.org said:

 i just tried to compile the 2.0.22 version on Mac OS X 10.8.5 with XCode 5.0.

This is known.  See for example bug 1541.  Sorry, I can't do anything
about it until someone provides a tested solution.

 signal.c:125:41: warning: adding 'int' to a string does not append to the 
 string
   [-Wstring-plus-int]
   write (2, 0123456789+(value/i), 1);
 ^~
 signal.c:125:41: note: use array indexing to silence this warning

Surely, it does not.  Syntactic sugar is required to drink from this
source - stupid warning.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users