public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Lutz v. Grafenstein" <lutz.von.grafenstein@orcsoftware.com>
To: Pthreads-Win32 list <pthreads-win32@sourceware.org>
Cc: "Lutz v. Grafenstein" <lutz@orcsoftware.com>
Subject: Re: compiling problems using pthreads with mingw 4.2.3 g++
Date: Sat, 06 Jan 2007 16:18:00 -0000	[thread overview]
Message-ID: <459FCB29.6090000@orcsoftware.com> (raw)
In-Reply-To: <459FB7A5.60104@orcsoftware.com>

Please disregard my last post: i found that macro definitions (clashing 
with windows stuff) included before pthreads caused the mentioned 
problems with pthreads release 2-8-0. no problems so far when removing 
the macros.

Cheers,

Lutz

Lutz v. Grafenstein schrieb:

> Dear all
>
> using pthreads with mingw g++ (version3.4.2) i end with strange 
> compiler errors. i do not have those issues with gcc (i.e. C code, not 
> C++), or also VC++. also similar  code compiled fine on a linux 
> machine/SUSE 9.1/g++.
>
> maybe this is a known issue? the errors below are produced with an 
> older snapshot of the headers, but with  the latest release 2-8-0 i 
> get get similar problems in oleidl.h: here i suspect something wrong 
> with the windows.h or make i am using (it is from the mingw 
> distribution), but have no evidence.
>
> thanks,
>
> Lutz
> *****************************************************************
>
> ../../Libraries/pthreads/include/sched.h:301: error: expected `)' 
> before '=' tok
> en
> ../../Libraries/pthreads/include/sched.h:301: error: expected `,' or 
> `;' before
> '=' token
> In file included from ../../Libraries/Hash.h:19,
>                from ShadowMarket.cpp:23:
> ../../Libraries/pthreads/include/pthread.h:1349: error: expected 
> unqualified-id
> before '{' token
> ../../Libraries/pthreads/include/pthread.h:1349: error: expected `,' 
> or `;' befo
> re '{' token
> ../../Libraries/pthreads/include/pthread.h:2163: error: expected `)' 
> before '='
> token
> ../../Libraries/pthreads/include/pthread.h:2163: error: expected `,' 
> or `;' befo
> re '=' token
> ../../Libraries/pthreads/include/pthread.h:2213: error: expected 
> class-name befo
> re '{' token
> ../../Libraries/pthreads/include/pthread.h:2215: error: expected 
> class-name befo
> re '{' token



-- 


Lutz v. Grafenstein
Trading Software Analyst

--------------------
Orc Software GmbH,
A-1010 Wien, Tuchlauben 14/9

Telefon: +43 1 5126993
Fax: +43 907 67 55

www.orcsoftware.com

      reply	other threads:[~2007-01-06 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06 14:52 Lutz v. Grafenstein
2007-01-06 16:18 ` Lutz v. Grafenstein [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=459FCB29.6090000@orcsoftware.com \
    --to=lutz.von.grafenstein@orcsoftware.com \
    --cc=lutz@orcsoftware.com \
    --cc=pthreads-win32@sourceware.org \
    /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).