From: Michel <michel.pacilli@free.fr>
To: pthreads-win32@sourceware.org, Kai Tietz <ktietz70@googlemail.com>
Subject: Re: [patch] Support for x64 Windows
Date: Sun, 14 Feb 2010 14:56:00 -0000 [thread overview]
Message-ID: <4B780F27.5010703@free.fr> (raw)
In-Reply-To: <90baa01f0908120123mdad28able9ef0640cc681217@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'd like to use pthreads-w32 with a 64 bits windows... and well i'm a
not a guru with coders tools like "patch" (svn and so on...)
it seems that this patch is not applied in the cvs tree, could you
explain me how to do ?
do i need to install cygwin tools, or msys ?
is it possible to do it without ?
how do i modify the nmakefile to be 64 bits able ?
well, i know i ask a lot, but i'm feeling unuseful ... i'd like to help!
just tell me how :)
the 64bits step is very important for a lot of applications, and this
library is so useful, i'd like to continue to use a so clean thread code
with 64 bits platforms.
with my best regards,
michel pacilli
Le 12/08/2009 10:23, Kai Tietz a écrit :
> 2009/6/22 Kai Tietz <ktietz70@googlemail.com>:
>> 2009/6/22 Ross Johnson <Ross.Johnson@homemail.com.au>:
>>> Kai Tietz wrote:
>>>>
>>>> PING?
>>>>
>>>
>>> PONG :-)
>>>
>>> I don't have the technology to confirm the patch with a build and
>>> run, but I
>>> will run an eye over it ASAP.
>>>
>>> Regards.
>>> Ross
>>>
>>
>> Thanks, if you need tests or assistant, don't hesitate to ask me, or
>> visit our IRC channel on irc://irc.oftc.net/mingw-w64
>>
>> Regards,
>> Kai
>>
>> --
>> | (\_/) This is Bunny. Copy and paste
>> | (='.'=) Bunny into your signature to help
>> | (")_(") him gain world domination
>>
> Hello,
>
> I just would like to ask, if there is a chance that this patch get
> reviewed?
>
> Best regards,
> Kai
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJLeA8nAAoJEIhxgwX9raOW4qoIALjiHDUfUImugOSk96hqKuDS
VzshrDHNHmxh1IHtDY7ZEwtiYr5KInWdv3wDDoCMbWlYfqQQ2GRzPknnJ486p1bN
Z5e/zwrXOIF0EGL5vLzhQWAgU7C6OAJzSJt8DFeSzwDvkQljtAaRye/K1nG2QmJE
Lubp3GR+LLiqvrJbk10OItrh/OKbPaFG2IjBjRUkMATuHLPTxqntYtlNGUfXhK7P
8zUZ2hAd94dT+++EYydl/9WOUJMSNqHP4Ggk3jXq0rmLjWzy2B95KE0M9kLKbfx3
6nwOZ3X6/2mtOf0IKVE6QifYe/e5U/0MgnfiCdCsSGJyGNZ8GT1WMl4Q95/pOj4=
=mhUC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-14 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 20:19 Kai Tietz
2009-06-22 7:36 ` Kai Tietz
2009-06-22 8:40 ` Ross Johnson
2009-06-22 8:43 ` Kai Tietz
2009-08-12 8:24 ` Kai Tietz
2010-02-14 14:56 ` Michel [this message]
2009-09-12 10:46 xxcv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B780F27.5010703@free.fr \
--to=michel.pacilli@free.fr \
--cc=ktietz70@googlemail.com \
--cc=pthreads-win32@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).