Front page | perl.perl5.porters |
Postings from September 2011
RE: generating win32/config_H.*
Thread Previous
|
Thread Next
From:
Steve Hay
Date:
September 1, 2011 07:14
Subject:
RE: generating win32/config_H.*
Message ID:
1B32FF956ABF414C9BCE5E487A1497E70AE2CCC0@ukmail02.planit.group
H.Merijn Brand wrote on 2011-09-01:
>> Btw, Merijn: One of the manual parts of the process of updating them
is
>> restoring QUADKIND 5 (QUAD_IS___INT64), which gets lost when running
>> win32/config_h.PL because it isn't in config_h.SH. Is that something
>> that you could sort out?
> Will be in my next update. Metaunit now updated.
> http://perl5.git.perl.org/metaconfig.git/commit/55db06f7a3707318f9094c
>
Thanks.
>> (It was added to the win32 configs long ago in 83ff24d4e9, but never
>> found its way upstream.)
>
> I'm not "triggered" by changes to win32 files :)
>
;-)
> I don't see how this change ought to make it into meta:
>
> --- a/win32/config_H.vc
> +++ b/win32/config_H.vc
> @@ -909,22 +909,25 @@
> /* HAS_QUAD:
> * This symbol, if defined, tells that there's a 64-bit integer
> type, * Quad_t, and its unsigned counterpar, Uquad_t. QUADKIND
> will be
> one - * of QUAD_IS_INT, QUAD_IS_LONG, QUAD_IS_LONG_LONG, or
> QUAD_IS_INT64_T. + * of QUAD_IS_INT, QUAD_IS_LONG,
> QUAD_IS_LONG_LONG, QUAD_IS_INT64_T. + * or QUAD_IS___INT64.
> */
> -/*#define HAS_QUAD /**/
> +#define HAS_QUAD /**/
> #ifdef HAS_QUAD # ifndef __GNUC__ # define Quad_t __int64
/**/
> # define Uquad_t unsigned __int64 /**/ +# define QUADKIND 5
> /**/ # else # define Quad_t long long /**/ # define
> Uquad_t unsigned long long /**/ +# define QUADKIND 3
> /**/ # endif -# define QUADKIND 5 /**/ # define QUAD_IS_INT 1
#
> define QUAD_IS_LONG 2 # define QUAD_IS_LONG_LONG 3 #
> define QUAD_IS_INT64_T 4 +# define QUAD_IS___INT64 5 #endif
>
[Hmm. Outlook's screwy quoting doesn't like that does it?!]
It was just the QUAD_IS___INT64 definition (and comment) that I wanted
for now, as you've done.
There are numerous __GNUC__ tests throughout the VC++ files to support
building XS extensions with GCC in a perl (e.g. ActivePerl) that was
built with VC++, and likewise numerous _MSC_VER tests throughout the GCC
files. I don't really have a plan for handling them at the moment, other
than manually restoring them each time they've been regenerated by
win32/config_h.PL...
(Are there any precedents outside of Win32 for anything similar?)
Thread Previous
|
Thread Next