From: Thomas Pfaff <tpfaff@gmx.net>
To: npf@databackbone.dk
Cc: pthreads-win32@sources.redhat.com
Subject: Re: gcc version and __declspec
Date: Fri, 06 Dec 2002 03:35:00 -0000 [thread overview]
Message-ID: <Pine.WNT.4.44.0212061229320.249-100000@algeria.intern.net> (raw)
In-Reply-To: <OF8126AEAA.D70DE672-ON41256C87.003E21EA@databackbone.dk>
According to your path i assume that you are using the djgpp gcc.
This compiler does not built WIN32 executables but 32 bit DPMI
applications. To use pthreads-win32 with gcc get the mingw package from
http://www.mingw.org.
Thomas
On Fri, 6 Dec 2002 npf@databackbone.dk wrote:
> I have browsed the mailing list archives for info - ahem..but
>
> I'm new to the whole GNU thing - been working with M$ VC6+ - so bear
> with
> me :)
>
> Well, I get the following compiler error :
>
> H:\AIX\GNU\DJGPP>gxx -c -Wall include\cdb\component.cpp
>
> In file included from include/threads/pthreads/pthread.h:244,
> from include/cdb/component.h:52,
> from include/cdb/component.cpp:543:
> include/threads/pthreads/sched.h:70:3: #error Please upgrade your GNU
> compiler to one that supports __declspec.
>
> I use gcc version 3.2.1 (the latest) - so I'm a little confused..
>
> should some dll's be installed as well for pthread?
> ------------------------------------------------------------------------
> -------------
>
> Niels Peter Frandsen
> M.Sc.Physics, Ba.Sc.Comp
> Senior Developer @
> ------------------------------------------------------------------------
> -------------
>
> Data Backbone Software A/S
> npf@databackbone.com
> http://www.databackbone.com
> /** Linking Software Together */
>
>
next prev parent reply other threads:[~2002-12-06 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 3:26 npf
2002-12-06 3:35 ` Thomas Pfaff [this message]
2002-12-06 4:56 npf
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.WNT.4.44.0212061229320.249-100000@algeria.intern.net \
--to=tpfaff@gmx.net \
--cc=npf@databackbone.dk \
--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).