public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: Immanuel Dold <ihd2008@live.de>
Cc: pthreads-win32@sourceware.org
Subject: Re: compiler error with vs 2008
Date: Wed, 30 Nov 2011 01:21:00 -0000	[thread overview]
Message-ID: <4ED584BF.70500@homemail.com.au> (raw)
In-Reply-To: <BLU0-SMTP4723444EBED8A234850262AACB30@phx.gbl>

On 30/11/2011 7:53 AM, Immanuel Dold wrote:
> Hello everybody.
>
> I am new to this project but I need help. I am a German student and I am
> currently working with PTAM and libcvd. The program I am building works
> fine under windows 7 32-bit. The problem is that my tutor for my thesis
> works with windows 7 64-bit. You are probably guessing right that on
> that machine the program only hangs. I get a 100% processor load but the
> program not even gets to the main() function. Until now I used pthread
> 2.8.0 and after some research on the net I found out that I have to use
> more recent code. Since there is no release I tried to build my own
> libraries.

You do need to use the latest cvs version for 64 bit builds.

>
> This is why I looked up for wincvs and checked out the newest code from
> the server. I looked into the README file for instructions on how to
> build all the .lib and .dll files. Now there is my problem. Using nmake
> from Visual Studio 2008 Pro with the parameters "clean VC" and "clean
> VSE" works just fine. But libcvd and PTAM rely both on the VCE version
> and so I tried "nmake clean VCE" and there I got stuck. The compiler
> throws errors (C2264) in "ptw32-MCS_lock.c" in lines 108, 127, 136, 197
> and 215 saying that the it can not cast "volatile size_t *" into
> "volatile LONG *".

You may find that using the VC build works with your application. The 
VCE version has problems anyway and is not really recommended.

This problem has been reported to me by Daniel Richard G. who has also 
provided a substantial patch that also includes a large number of other 
changes not necessarily related to this issue. Unfortunately I just 
don't have the time now or the [64 bit MSVS] tools to properly 
incorporate and test complex patch sets or coordinate those who do, 
considering that this project aims to work with several compilers (e.g. 
MS and GNU) and their various versions and supported architectures.

But I do want to note here that the current code in cvs has been built 
and well tested on several 64 bit systems and compilers, but presumably 
not using this specific MSVC++ compiler version.

I don't know if this link helps at all with the cast error, i.e. adding 
the /DNO_STRICT compiler option to the compiler flags in the nmake Makefile:

http://msdn.microsoft.com/en-us/library/aa383679%28v=vs.85%29.aspx

Regards.
Ross

  reply	other threads:[~2011-11-30  1:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 20:52 Immanuel Dold
2011-11-30  1:21 ` Ross Johnson [this message]
2011-11-30 12:28   ` Immanuel Dold
2011-12-01  1:38     ` Ross Johnson
2011-12-03 11:42       ` Immanuel Dold
     [not found]         ` <4EDB6750.5060900@homemail.com.au>
2011-12-04 17:10           ` Immanuel Dold
2012-01-18 12:56           ` Immanuel Dold
2012-01-19  1:30             ` Ross Johnson
2012-01-19 17:58               ` Immanuel Dold
2012-01-20  2:18                 ` Ross Johnson

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=4ED584BF.70500@homemail.com.au \
    --to=ross.johnson@homemail.com.au \
    --cc=ihd2008@live.de \
    --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).