public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Philip Van Hoof <spam@pvanhoof.be>
To: Marcel Ruff <mr@marcelruff.info>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: Trying to get pthread-win32 compiling for WinCE
Date: Thu, 28 Dec 2006 22:02:00 -0000	[thread overview]
Message-ID: <1167343342.4875.35.camel@lort> (raw)
In-Reply-To: <1167342425.4875.31.camel@lort>

On Thu, 2006-12-28 at 22:47 +0100, Philip Van Hoof wrote:

> > i have compiled the patched pthreads successfully for Windows CE with 
> > ARM processor.
> > 
> > Download the patch for Windows CE from
> >    http://www.xmlBlaster.org/wince/pthreads-2006-11-29.patch
> > and apply it on pthreads 2.7.0 or better the cvs checkout from 2006-11-29.
> 
> Oh, cool and thanks.
> 
> I will of course check it out.

Right, the patch basically fixes the same problems that I encountered,
but then in a clean (ifdef-else-endif) way :-)

With the patch, I still get this problem:

C:\cygwin\home\Philip Van Hoof\pthreads>nmake VC

Microsoft (R) Program Maintenance Utility   Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

        rc /dPTW32_RC_MSC /d__CLEANUP_C version.rc
version.rc(33) : fatal error RC1015: cannot open include file 'winver.h'.
NMAKE : fatal error U1077: 'rc' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft eMbedded C++ 4.0\Common
EVC\Bin\NMAKE.EXE"' : return code '0x2'
Stop.

C:\cygwin\home\Philip Van Hoof\pthreads>


-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://www.pvanhoof.be/blog




      reply	other threads:[~2006-12-28 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 21:04 Philip Van Hoof
2006-12-28 21:40 ` Marcel Ruff
2006-12-28 21:47   ` Philip Van Hoof
2006-12-28 22:02     ` Philip Van Hoof [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=1167343342.4875.35.camel@lort \
    --to=spam@pvanhoof.be \
    --cc=mr@marcelruff.info \
    --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).