Mailinglist Archive: opensuse-packaging (135 mails)
| < Previous | Next > |
[opensuse-packaging] Re: [opensuse-project] Procinfo and Procinfo-NG
- From: tabris <tabris@xxxxxxxxxx>
- Date: Wed, 22 Aug 2007 21:48:45 -0700
- Message-id: <46CD11AD.6030606@xxxxxxxxxx>
Cristian Rodriguez wrote:
> tabris escribió:
>
>> So I'll be looking into those when I get a chance.
>>
>
> good, then we can continue discussion on the opensuse-packaging list, we
> are offtopic here in -project. ;-)
>
Ok, I applied the patch provided to my SVN repo
http://svn.tabris.net/repos/procinfo-ng/ to trunk/
As to the warnings, they look bogus to me.
I'm using int64_t and uint64_t. It looks like to be silence the
warnings, I'd need to do any of the following:
a) do my own typedefs. blecch, plus might be non-portable.
b) use different sprintf statements depending on __WORDSIZE. that's not
much better
# if __WORDSIZE == 64
typedef long int int64_t;
# else
__extension__
typedef long long int int64_t;
# endif
#if __WORDSIZE == 64
typedef unsigned long int uint64_t;
#else
__extension__
typedef unsigned long long int uint64_t;
#endif
> tabris escribió:
>
>> So I'll be looking into those when I get a chance.
>>
>
> good, then we can continue discussion on the opensuse-packaging list, we
> are offtopic here in -project. ;-)
>
Ok, I applied the patch provided to my SVN repo
http://svn.tabris.net/repos/procinfo-ng/ to trunk/
As to the warnings, they look bogus to me.
I'm using int64_t and uint64_t. It looks like to be silence the
warnings, I'd need to do any of the following:
a) do my own typedefs. blecch, plus might be non-portable.
b) use different sprintf statements depending on __WORDSIZE. that's not
much better
# if __WORDSIZE == 64
typedef long int int64_t;
# else
__extension__
typedef long long int int64_t;
# endif
#if __WORDSIZE == 64
typedef unsigned long int uint64_t;
#else
__extension__
typedef unsigned long long int uint64_t;
#endif
| < Previous | Next > |