Hello niXman!

On Fri, Sep 30, 2011 at 12:04 AM, niXman <i.nix...@gmail.com> wrote:
> I have rebuilt with usage pthreads-win32 - there was other error. In
> general I was tangled...

I don't understand exactly what you are saying.  When you say
"with usage pthreads-win32", what do you mean?

When you say "in general I was tangled", could you give a short
explanation of some of the problems you are having?

If you are trying to use pthreads-win32 to get std::thread working
with mingw-w64, I gave some instructions in an earlier post:

   http://sourceforge.net/mailarchive/message.php?msg_id=26533138

(If I remember correctly, I cross-posted this, so you probably can also
find this post in the mingw-w64-public archive.)

Note (See point 4 in the post.) that the compile command does not
require the "-static" flag (if I recall correctly that this was your issue).

> I will ask once again: Somebody tried to understand in what the bug reason?
>
> niXman.

Good luck, and...

Happy Hacking!


K. Frank


> 2011/9/28 niXman <i.nix...@gmail.com>:
>> Hi Frank.
>>
>>>
>>> (niXman...  Is that supposed to be some kind of superhero?)
>>
>> No. It`s from the "Man who always uses the *nix" platform =)
>>>
>>> niXman, if your use case is to use std::thread with mingw-w64 and
>>> pthreads-win32, I should be able to refer you to some earlier posts that
>>> show how to do it, and could probably give you some pointers if you
>>> hit snags.
>>
>> Thanks anticipatorily.
>>    niXman.
>> ...

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to