[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: determining 32 v. 64 bit compilatio
From: |
Wesley Smith |
Subject: |
Re: determining 32 v. 64 bit compilatio |
Date: |
Wed, 30 Jun 2010 16:37:09 +0200 |
On Wed, Jun 30, 2010 at 3:51 PM, John Calcote <address@hidden> wrote:
> On 6/30/2010 3:48 AM, Andrew W. Nosenko wrote:
>>
>> Excuse me, but why just don't
>>
>> #include <inttypes.h>
>>
>> and use int32_t and uint32_t declared there?
>>
>> If you want to deal with some heavy non-posix, or just too old system, then
>>
>> AC_TYPE_INT32_T
>>
>> autoconf macro (and like) may help you.
>>
>>
>
> He said it was in a third-party open source library. I'm guessing he
> feels he doesn't have the right to change that code.
Exactly. I don't want to fork the code for something like this. It's
easier to just provide the proper compile flag.
wes
- determining 32 v. 64 bit compilatio, Wesley Smith, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Bob Friesenhahn, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Mike Frysinger, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Wesley Smith, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Mike Frysinger, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Wesley Smith, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Raphael 'kena' Poss, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Wesley Smith, 2010/06/30
- Re: determining 32 v. 64 bit compilatio, Andrew W. Nosenko, 2010/06/30
- Re: determining 32 v. 64 bit compilatio, John Calcote, 2010/06/30
- Re: determining 32 v. 64 bit compilatio,
Wesley Smith <=
- Re: determining 32 v. 64 bit compilatio, Peter O'Gorman, 2010/06/30
- Re: determining 32 v. 64 bit compilatio, Bob Friesenhahn, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Mike Frysinger, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Russ Allbery, 2010/06/29
- Re: determining 32 v. 64 bit compilatio, Bob Friesenhahn, 2010/06/29