From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Martin van den Nieuwelaar <martin@gadgets.co.nz>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: PThreads under win95 linked to missing export
Date: Tue, 14 Aug 2001 19:35:00 -0000 [thread overview]
Message-ID: <3B79DFE6.E968E7A4@ise.canberra.edu.au> (raw)
In-Reply-To: <3B79B6E3.3D17A4B2@gadgets.co.nz>
Martin van den Nieuwelaar wrote:
>
> I guess the more general question then is, is it intended that
> pthreads works only under 98 or later? How about NT? Was there ever
> a version for 95? I haven't seen any docs that mention which windows
> platforms it works on. I just want to know before I release my app as
> "works under windows" and then find out I have hundreds of users
> sending me hate mail because it clearly doesn't work on their system.
> :)
I must have missed checking this before using
InterlockedCompareExchange in the barrier and spinlock routines
that were added at snapshot 2001-07-12. I run the testsuite
on a Win98 machine before releasing snapshots.
Snapshot 2001-07-03 should be OK to use. Apart from not having
spinlocks and barriers, there are only a few minor bug fixes
that are the difference.
I'll have to fix this for the next snapshot so that Win95 and
pre-NT4.0 is properly supported again.
Thanks for pointing out the error.
Ross
>
> Regards,
>
> -Martin
>
> reentrant wrote:
> >
> > The source of the problem appears to be that InterlockedCompareExchange()
> > "Requires Windows 98 or later" (according to MSDN).
> >
> > Dave
> >
> > --- Martin van den Nieuwelaar <martin@gadgets.co.nz> wrote:
> > > Hi People,
> > >
> > > I'm new to this list and have recently started using pthreads-win32 so
> > > I could port some UNIX software to the windows environment.
> > >
> > > One problem I have run into is a missing export error. If I take my
> > > app (compiled under win98 SE using ms vc++ 6.0) and pthreadvce.dll
> > > file and put them on a win95 machine (Version 4.00.950B), I get the
> > > following error:
> > >
> > > The PTHREADVCE.DLL file is linked to missing export
> > > KERNEL32.DLL:InterlockedCompareExchange
> > >
> > > I looked around on the web, and also in the mailing list archives, but
> > > found no reference to this error. Any thoughts on what might be the
> > > source of my problem, and how to fix it?
> > >
> > > TIA,
> > >
> > > -Martin
>
> --
> Expert carrier network traffic analysis and visualisation
> http://www.gadgets.co.nz/products.shtml
> xenaphobia: The fear of being beaten to a
> pulp by a leather-clad, New Zealand woman
--
+-------------------------+---+
| Ross Johnson | | "Come down off the cross
| Management & Technology |___| We can use the wood" - Tom Waits
| Building 11 |
| University of Canberra | eMail: rpj@ise.canberra.edu.au
| ACT 2601 | WWW:
http://public.ise.canberra.edu.au/~rpj/
| AUSTRALIA |
+-----------------------------+
next prev parent reply other threads:[~2001-08-14 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <997828638.29731.ezmlm@sources.redhat.com>
2001-08-14 15:49 ` Martin van den Nieuwelaar
2001-08-14 16:21 ` reentrant
2001-08-14 16:40 ` Martin van den Nieuwelaar
2001-08-14 19:35 ` Ross Johnson [this message]
2001-08-15 13:20 van Lieshout, Fred
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=3B79DFE6.E968E7A4@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=martin@gadgets.co.nz \
--cc=pthreads-win32@sources.redhat.com \
/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).