Anthony Baxter wrote:
> On Saturday 22 April 2006 15:27, Neal Norwitz wrote:
>> In case it wasn't clear, the /Wp64 flag is available in icc
>> (Intel's C compiler).
>
> Is it worth turning this on for the icc ubuntu buildbot? Anyone got
> ideas on the best way to do this? Should I just set CFLAGS
On Saturday 22 April 2006 15:27, Neal Norwitz wrote:
> In case it wasn't clear, the /Wp64 flag is available in icc
> (Intel's C compiler).
Is it worth turning this on for the icc ubuntu buildbot? Anyone got
ideas on the best way to do this? Should I just set CFLAGS="-Wp64"
before running the bui
On 4/21/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz wrote:
> >> Right - they have been there ever since I started (in fact, I started
> >> this entire project *because* of these warnings). You can get them on
> >> x86, too, if you enable /Wp64.
> >
> > In case it wasn't clear, t
Neal Norwitz wrote:
>> Right - they have been there ever since I started (in fact, I started
>> this entire project *because* of these warnings). You can get them on
>> x86, too, if you enable /Wp64.
>
> In case it wasn't clear, the /Wp64 flag is available in icc (Intel's C
> compiler).
It still
On 4/21/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Thomas Heller wrote:
> > I forgot to mention that there are a lot of warnings about conversion
> > betweem Py_ssize_t to int - if you want me to fix the obvious ones
> > I'll offer to correct some of them from time to time and commit the
>
Thomas Heller wrote:
> I forgot to mention that there are a lot of warnings about conversion
> betweem Py_ssize_t to int - if you want me to fix the obvious ones
> I'll offer to correct some of them from time to time and commit the
> changes.
Right - they have been there ever since I started (in f
Thomas Heller wrote:
> Martin v. Löwis wrote:
>> Thomas Heller wrote:
>>> On XP (32-bit), I can compile python25.dll and python.exe for AMD64 now,
>>> after adding bufferoverflowU.lib to the linker options.
>> On what project? There should be /GS- options on all projects that need
>> it, which, in
Martin v. Löwis wrote:
> Thomas Heller wrote:
>> On XP (32-bit), I can compile python25.dll and python.exe for AMD64 now,
>> after adding bufferoverflowU.lib to the linker options.
>
> On what project? There should be /GS- options on all projects that need
> it, which, in turn, should result in bu
Thomas Heller wrote:
> On XP (32-bit), I can compile python25.dll and python.exe for AMD64 now,
> after adding bufferoverflowU.lib to the linker options.
On what project? There should be /GS- options on all projects that need
it, which, in turn, should result in bufferoverflowU.lib not being neede
Martin v. Löwis wrote:
> Thomas Heller wrote:
return Py_BuildValue("s",
ver.dwMajorVersion,
ver.dwMinorVersion,
ver.dwBuildNumber,
ver.dwPlatformId,
Thomas Heller wrote:
>>> return Py_BuildValue("s",
>>> ver.dwMajorVersion,
>>> ver.dwMinorVersion,
>>> ver.dwBuildNumber,
>>> ver.dwPlatformId,
>>> ver.szCSDVersion);
Martin v. Löwis wrote:
> Thomas Heller wrote:
>> In sys_getwindowsversion:
>>
>> return Py_BuildValue("s",
>> ver.dwMajorVersion,
>> ver.dwMinorVersion,
>> ver.dwBuildNumber,
>> ver.dwPlatfor
Thomas Heller wrote:
> In sys_getwindowsversion:
>
> return Py_BuildValue("s",
> ver.dwMajorVersion,
> ver.dwMinorVersion,
> ver.dwBuildNumber,
> ver.dwPlatformId,
>
Martin v. Löwis wrote:
> Thomas Heller wrote:
>> Is this no longer available?
>
> Sorry, I just deleted that. I now replaced it with
> python-2.5.13231.amd64.msi
Thanks, I'll try that.
>> BTW: When I build Python for ReleaseAMD64 myself, the exe crashes at the
>> first
>> Py_BuildValue call.
>
Thomas Heller wrote:
> Is this no longer available?
Sorry, I just deleted that. I now replaced it with
python-2.5.13231.amd64.msi
> BTW: When I build Python for ReleaseAMD64 myself, the exe crashes at the first
> Py_BuildValue call.
That doesn't happen for me... can you find out why it crashes?
Martin v. Löwis wrote:
> I have now produces a snapshot of a Win64 build for AMD64
> processors (also known as EM64T or x64); this is different
> from IA-64 (which is also known as Itanium)...
>
> Anyway, the binaries are
>
> http://www.dcl.hpi.uni-potsdam.de/home/loewis/python-2.5.13199.amd64.ms
Trent Mick wrote:
> Look for:
> def find_platform_sdk_dir()
> here:
> http://cvs.sourceforge.net/viewcvs.py/pywin32/pywin32/setup.py?view=markup
>
> That is the best code I know for doing that.
Right; I was planning something similar (although I would probably
hard-code the 2003 SP1 regis
[Martin v. Loewis wrote]
> If you want to build extensions for this build using distutils, you
> need to
> ...
> 2. open an AMD64 retail shell
> ...
>
> It might be possible to drop 2) some day, but finding the SDK from
> the registry is really tricky.
Look for:
def find_platform_sdk_dir()
he
I have now produces a snapshot of a Win64 build for AMD64
processors (also known as EM64T or x64); this is different
from IA-64 (which is also known as Itanium)...
Anyway, the binaries are
http://www.dcl.hpi.uni-potsdam.de/home/loewis/python-2.5.13199.amd64.msi
This is from today's trunk. If you
19 matches
Mail list logo
