bug-cvs
[Top][All Lists]
Advanced

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

RE: Windows Build & Gnulib Problems - Feature Branch


From: Conrad T. Pino
Subject: RE: Windows Build & Gnulib Problems - Feature Branch
Date: Tue, 20 Sep 2005 08:59:16 -0700

Hi Derek,

> From: Derek Price
> Sent: Tuesday, September 20, 2005 06:17
> 
> I'll get back to this.  I'm investigating and think I need to bring this
> up with GNULIB.  If you want to add the following to lib/mbuiter.h for
> now, it should allow you to compile for now:
> 
> #if !defined mbsinit && !HAVE_MBSINIT
> # define mbsinit(ps) 1
> #endif

I assume you will commit a fix later so I will not commit this change.
This allows some forward movement but uncovers another issue.

The "wcwidth" function has no prototype but it links never the less.

--------------------Configuration: libcvs - Win32 Debug--------------------
Compiling...
strcasecmp.c
h:\conrad\projects\cvs-1.12\lib\mbchar.h(243) : warning C4013: 'wcwidth' 
undefined; assuming extern returning int
Creating library...
--------------------Configuration: libdiff - Win32 Debug--------------------
Creating library...
--------------------Configuration: cvsnt - Win32 Debug--------------------
Linking...

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

> >5. I can get down to the missing "mbinit" with the patch
> >at the end of this message.
> 
> Otherwise, your patch looks fine, except for these warnings:

Those were compile errors with EMPTY "sys/socket.h" and "netdb.h" files.

> The fact that declarations for gethostbyname & getservbyname are not
> found by the time they are encountered implies that either <winsock2.h>
> is not being included or something is suppressing the processing of
> these declarations in this header.  This should probably be fixed, even
> if it does link anyhow.

Once "sys/socket.h" contains

        #define WIN32_LEAN_AND_MEAN 1
        #include <winsock2.h>

        typedef size_t socklen_t;

everything looks better.

We need to look at HAVE_IPV4 and related.  I'll follow up later.

> Thanks,

You're welcome,

> Derek

Conrad





reply via email to

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