public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Makoto Kato <makoto.2000@gmail.com>
To: "Reavely, Simon P" <Simon.Reavely@comverse.com>
Cc: Randy Howard <randy.howard@megapathdsl.net>,
	 	"Phil Frisbie, Jr." <phil@hawksoft.com>,
	 	pthreads-win32@sources.redhat.com
Subject: Re: pthreads for WindowsXP 64-bit
Date: Sat, 11 Feb 2006 03:01:00 -0000	[thread overview]
Message-ID: <bed95a0a0602101901o64080ce0g362e0bdb20cf26cb@mail.gmail.com> (raw)
In-Reply-To: <A7CEA0F211E33F4B82C535D784AAD2F001780A5B@cmaexch02.csg.csgsystems.com>

Hi, Simon.

Although I don't test on latest CVS, there is x64 source / binaries of
old CVS tree into buildtools64 for Mozilla on
http://www.mozilla-x86-64.com/download.html.  This source code is
included on current CVS.


-- Makoto Kato / makoto.2000@gmail.com

On 2/11/06, Reavely, Simon P <Simon.Reavely@comverse.com> wrote:
> Hi,
>
> I am trying to get a 64 compile of pthread-win32 on 64 bit opteron. Has
> anyone performed a successful port?
>
> Cheers,
> Simon
> p.s. I found the email below in the email list history but no follow-up.
>
>
>
> Simon Reavely
> Mgr, Systems Architecture
> Office: +1 617 273 5370
>
> -----Original Message-----
> From: Randy Howard [mailto:randy.howard@megapathdsl.net]
> Sent: Wednesday, November 19, 2003 9:05 PM
> To: 'Phil Frisbie, Jr.'
> Cc: pthreads-win32@sources.redhat.com
> Subject: RE: pthreads for WindowsXP 64-bit
>
>
> I can't remember offhand the exact specifics, it was a while back and I
> blew it off for a while.  I'll try to get back to it in the next few
> days and capture the results.
>
>
> Randy Howard
> randy.howard@megapathdsl.net
>
>
> > -----Original Message-----
> > From: pthreads-win32-owner@sources.redhat.com
> > [mailto:pthreads-win32-owner@sources.redhat.com] On Behalf Of Phil
> > Frisbie, Jr.
> > Sent: Wednesday, November 19, 2003 10:17 AM
> > Cc: pthreads-win32@sources.redhat.com
> > Subject: Re: pthreads for WindowsXP 64-bit
> >
> >
> > Randy Howard wrote:
> > > Good luck getting an answer on this one.. :-)
> > >
> > > I asked the same thing (for both Opteron and Itanium) here
> > and several
> > > other places, such as comp.programming.threads, and in all cases it
> > > has been completely ignored.
> >
> > What problems have you run into when compiling for WIN64?
> >
> > > Randy Howard
> > > randy.howard@megapathdsl.net
> >
> > --
> > Phil Frisbie, Jr.
> > Hawk Software
> > http://www.hawksoft.com
> >
>
>


--
-- Makoto Kato / makoto.2000@gmail.com / raven@oldskool.jp

  reply	other threads:[~2006-02-11  3:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  2:54 Reavely, Simon P
2006-02-11  3:01 ` Makoto Kato [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-19 14:19 Jef Gearhart
2003-11-18 18:54 Aptech Systems Tech Support
2003-11-19  6:41 ` Randy Howard
2003-11-19 16:16   ` Phil Frisbie, Jr.
2003-11-20  2:05     ` Randy Howard

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=bed95a0a0602101901o64080ce0g362e0bdb20cf26cb@mail.gmail.com \
    --to=makoto.2000@gmail.com \
    --cc=Simon.Reavely@comverse.com \
    --cc=phil@hawksoft.com \
    --cc=pthreads-win32@sources.redhat.com \
    --cc=randy.howard@megapathdsl.net \
    /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).