public inbox for
 help / color / mirror / Atom feed
From: "George Mardale" <>
To: <>
Subject: Re: problems linking
Date: Mon, 03 May 2004 06:25:00 -0000	[thread overview]
Message-ID: <002601c430d7$74a6d910$4f64a8c0@firebird> (raw)
In-Reply-To: <>

Hi Ross,

Thanks for your recommendations... I will try to follow them...

As of your assumption, you were right. I really thought the 'CE' in
pthreadVCE.lib came from winCE :-). Thanks for clarifying this also.

Best regards,

----- Original Message -----
From: "Ross Johnson" <>
To: "George Mardale" <>
Sent: Saturday, May 01, 2004 5:39 AM
Subject: Re: problems linking

> George,
> Thanks for confirming that the WinCE build works OK. As I said, I have
> no way of testing this version myself.
> Since you're building the library from source, can I recommend grabbing
> the sources from CVS (if you aren't already), since these include one or
> two bug fixes that aren't in the snapshot yet. Details for anonymous CVS
> downloading are on the project web page:
> Would I be correct in thinking that you thought the 'CE' in
> pthreadVCE.lib meant WinCE? That never occurred to me. It actually
> indicates that this is the version built using C++ Exceptions. See the
> README and FAQ files for the whole history of the naming of prebuilt
> libraries and the issues relating to using C++ exceptions, Structured
> exceptions, or plain C set/longjmp in the context of POSIX threads and
> it's portability amongst Pthreads implementations.
> The recommended version is plain C. This is the one that will be built
> from source unless you go to the trouble of setting an additional
> compile time macro.
> Regards.
> Ross
> George Mardale wrote:
> >Hi again,
> >
> >I managed to solve the problem. Thanks to Ross Johnson for pointing out
> >correct approach. I use eVC++ and I used the prebuilt binaries, which I
> >thouhght were for wince, but they weren't.
> >
> >After recompiling the wince port of pthreads-win32 (+ setting the proper
> >#define-s), it worked...
> >
> >Thanks again for your support, guys.
> >Best regards,
> >George.
> >
> >

  parent reply	other threads:[~2004-05-03  6:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30  4:32 Vikas Gandhi
2004-04-30  6:32 ` George Mardale
     [not found]   ` <>
2004-05-03  6:25     ` George Mardale [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-29  4:57 Vikas Gandhi
2004-04-29 11:05 ` George Mardale
2004-04-28 15:59 George Mardale

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002601c430d7$74a6d910$4f64a8c0@firebird' \ \ \

* 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).