From: Michał Fryska <szumek@mud.pl>
To: Pthreads Developers List <pthreads-win32@sourceware.cygnus.com>
Subject: Re: Can I run pthread on win95?
Date: Sat, 25 Sep 1999 05:59:00 -0000 [thread overview]
Message-ID: <Pine.OSF.4.10.9909251436280.4137-100000@venus.wmid.amu.edu.pl> (raw)
In-Reply-To: <Pine.LNX.4.05.9909251319470.14272-100000@swan.canberra.edu.au>
On Sat, 25 Sep 1999, Ross Johnson wrote:
> > I've no problems with running it with Windows NT && cygwin-b20.
> > But.. the same program compiled under Windows 95 with cygwin-b19 doesn't
> > work at all. So... is there a chance to run it with W95??
>
> What happens when you run the executable built under WNT on W95?
> Ditto for the W95 built program running on WNT?
Ough, thanx! My problem was different, but this question solved my
problem (in some way)! 8-) When I run on w95 my programm built under WNT
(with cygwin-b20) everything seems to be alright. But.. still, the program
built under w95 doesn't work (it crashes while loading or initializing
pthreads.dll I think - it crashes EVEN if I do not call any function from
pthreads library. It crashes when I link it with libpthreads32.a
>
> The pthreads-win32 should not be causing problems under W95, but the
> library has not been tested with cygwin, only MSVC and Mingw32.
So.. as I see.. using pthreads32 with cygwin is on my own responsibility
:)
> - build libpthread32.a under W98 using Mingw32, then build and run
> the tests using Mingw32 on W98 using this libpthread32.a and the
> WNT/MSVC generated DLL.
But I still may use W95 instead of W98 I hope?
--
Szumek@mud.pl <-> Studnia Dusz < telnet://studnia.mud.pl:4000/ >
Pneumonoultramicroscopicsilicovolcanoconiosis is _too_ a word!
prev parent reply other threads:[~1999-09-25 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-23 11:04 Micha&lstrok
1999-09-23 15:45 ` WinCE Tristan Savatier
1999-09-24 22:29 ` Can I run pthread on win95? Ross Johnson
1999-09-25 5:59 ` Micha&lstrok [this message]
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=Pine.OSF.4.10.9909251436280.4137-100000@venus.wmid.amu.edu.pl \
--to=pthreads-win32@sourceware.cygnus.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).