public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Kerry.Barnes@gedae.com
Cc: pthreads-win32@sources.redhat.com
Subject: Re: PthreadVSE.dll or PthreadVCE.dll
Date: Wed, 03 Oct 2001 21:37:00 -0000	[thread overview]
Message-ID: <3BBBE767.729189DE@ise.canberra.edu.au> (raw)
In-Reply-To: <NOEIJHMKIKILFJOKONKMAECKCBAA.Kerry.Barnes@gedae.com>

Hi,

Generally it appears that there was a major change
between versions 5 and 6 of Visual Studio.
Pthreads-win32 pre-built dlls and libs are built
with MSVC 6.0.

Throwing some keywords at www.Google.com I found some
potentially useful information, suggesting that the
problem is in Visual Studio 5 - assuming that it's not
a simple disk full problem.

Here are some of the URLs that I found:

Suggests an internal VS bug with fix:-
http://www.cryer.co.uk/brian/mswinswdev/lnk1106ifodf.htm

Suggests that there is an incompatibility between
VS 5 and 6 libraries, and so building the library from
source using VS 5 may be the solution:-
http://www.catalyst.com/board/1/messages/1439.shtml

Many more links can be found here:-
http://www.google.com/search?q=fatal+error+LNK1106

Hope this helps.
Ross

Kerry Barnes wrote:
> 
> Hi
> 
> Does anyone have a solution for the problme given by Vianaya below.  I'm
> seeing exactly the same problem with WINNT4.0 and VC5.0 tools.   I've been
> able to link the pthreadVC.lib files using Windows 2000 and VC6.0 tools.  So
> I'm sure that I've downloaded the files correctly.
> 
> Kerry Barnes
> Blue Horizon Development Software, Inc.
> 18000 Horizon Way
> Mt Laurel, NJ 08054
> ----------------------------------------------------------------------
> PthreadVSE.dll or PthreadVCE.dll
> To: pthreads-win32 at sourceware dot cygnus dot com
> Subject: PthreadVSE.dll or PthreadVCE.dll
> From: Vinaya Thimmappa <vkt at india dot hp dot com>
> Date: Thu, 25 Jan 2001 11:11:43 +0530
> Organization: Hewlett Packard
> 
> Hi all,
> 
>    * I just downloaded the pthread-win32 library file .
>    * I am using WINNT4.0 with VC5.0 tool for compilation.
>    * I wrote a small program ,which  creates a simple mutex and then
>      destroys it
>    * It compiles fine .But after that is  the problem,
>    * while linking I got the following error:
>    * "pthreadVSE.lib : fatal error LNK1106: invalid file or disk full:
>      cannot seek to                 0x3a4c4c46"
>    * I added in projects-->settings->win32 debug->link ,the pthread.lib
>      file.
>    * The dll is in winnt/system32/ directory
>    * I have tried with both  pthreadVSE.dll and pthread.VCE.dll but
>      invain.
>    * Can anyone tell me why is this happening and how to rectify it .
> 
> Thanks
> Regards
> vinaya

-- 
+-------------------------+---+
| Ross Johnson            |   | "Come down off the cross
| Management & Technology |___|  We can use the wood" - Tom Waits
| Building 11                 |
| University of Canberra      | eMail: rpj@ise.canberra.edu.au
| ACT    2601                 | WWW:  
http://public.ise.canberra.edu.au/~rpj/
| AUSTRALIA                   |
+-----------------------------+

      reply	other threads:[~2001-10-03 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03  8:11 Kerry Barnes
2001-10-03 21:37 ` Ross Johnson [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=3BBBE767.729189DE@ise.canberra.edu.au \
    --to=rpj@ise.canberra.edu.au \
    --cc=Kerry.Barnes@gedae.com \
    --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).