bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken CVS tree?


From: Jerzy Kaczorowski
Subject: Re: Broken CVS tree?
Date: Thu, 21 Jun 2001 03:27:38 +0800

OK, it is better, but still cant pass the linking - here is what I am
getting now:

--------------------Configuration: cvsnt - Win32 Debug--------------------
Linking...
buffer.obj : error LNK2001: unresolved external symbol _shutdown
buffer.obj : error LNK2001: unresolved external symbol _S_ISSOCK
client.obj : error LNK2001: unresolved external symbol _S_ISSOCK
.\Debug\cvs.exe : fatal error LNK1120: 2 unresolved externals
Error executing link.exe.

cvs.exe - 4 error(s), 0 warning(s)

I also removed the #define NO_SOCKET_TO_FD 1
from the ccvs\windows-NT\config.h (could not find system.h) but with
similiar
errors:

--------------------Configuration: cvsnt - Win32 Debug--------------------
Linking...
buffer.obj : error LNK2001: unresolved external symbol _shutdown
buffer.obj : error LNK2001: unresolved external symbol _S_ISSOCK
.\Debug\cvs.exe : fatal error LNK1120: 2 unresolved externals
Error executing link.exe.

cvs.exe - 3 error(s), 0 warning(s)

Best Regards,
Jerzy

----- Original Message -----
From: "Derek R. Price" <dprice@collab.net>
To: "Larry Jones" <larry.jones@sdrc.com>
Cc: <jerzyk@wndtabs.com>; <bug-cvs@gnu.org>
Sent: Thursday, June 21, 2001 2:41 AM
Subject: Re: Broken CVS tree?


> Larry Jones wrote:
>
> > Jerzy Kaczorowski writes:
> > >
> > > --------------------Configuration: cvsnt - Win32
Debug--------------------
> > > Compiling...
> > > client.c
>
> [. . .]
>
> > Derek, this looks like a result of your changes a month and a half ago.
> > The errors are in the NO_SOCKET_TO_FD code that isn't used on Unix, so
> > it hasn't been noticed, but it's definitely broken.
>
> Yep.  That was my fault.  I applied a fix which compiled and passed
cursory
> tests (it updated itself from the server) on Linux but I don't have a
working
> Windows box to test on.
>
> The code still prints one extraneous warning which I'm not sure I'm ready
to get
> rid of.
>
> Interestingly enough, it looks like some of the windows code is actually
using
> sockets and FDs interchangably, so I'd be interested to hear what happens
if the
> #define NO_SOCKET_TO_FD line is commented out from windows-NT/system.h
before
> building.  It could be legacy...
>
> Checked in!  Thanks!
>
> Derek
>
> --
> Derek Price                      CVS Solutions Architect (
http://CVSHome.org )
> mailto:dprice@collab.net         CollabNet ( http://collab.net )
> --
> I will not drive the principal's car.
> I will not drive the principal's car.
> I will not drive the principal's car...
>
>           - Bart Simpson on chalkboard, _The Simpsons_
>
>
>
>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]