in reply to Re^2: length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR
in thread length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR

I'd hardly call a configuration option a hack. (I realise the procedure is different on Windows, but elsewhere it simply involves passing -Duse64bitall to Configure.)

Replies are listed 'Best First'.
Re^4: length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR
by syphilis (Archbishop) on Nov 08, 2010 at 02:25 UTC
    I'd hardly call a configuration option a hack

    Neither would I. (I chose the word carefully and deliberately.)

    The makefiles that ship with the source don't accommodate the option of building 64-bit integers into a 32-bit perl ... afaik you'd have to do some non-trivial hacking.

    Cheers,
    Rob
[reply]
      afaik you'd have to do some non-trivial hacking.

      Absolutely. I tried it once.

      We complain about the current 2106 warnings that the "successful build produces, you should see what happens when you try adding a few __int64 #defines/typedefs to the equation. Working what to change is impossible.

      Don't ya just love theoreticians :)

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
        Working what to change is impossible

        Yes, that was my feeling too after both of my attempts to build such a Win32 perl.

        I expected that the task should be much simpler now that the perl source has 64-bit config and config_H files in the win32 folder but, although they do the job for 64-bit builds, I was unable to coerce them into helping provide 64-bit integer support for 32-bit builds. (This could well be nothing more than ignorance on my part.)

        Cheers,
        Rob
[reply]

In Section Seekers of Perl Wisdom