Re: Latest failed compilation

On 29/09/13 20:40, Gregory M. Caughey wrote:
> On 9/29/2013 9:35 AM, Tony Mechelynck wrote:
>> On 29/09/13 17:32, Gregory M. Caughey wrote:
>>> Hi everybody,
>>> Since build 'Vim-7.4.041' my builds have been failing with error message
>>> "Makefile:2697: recipe for target `objects/mbyte.o' failed".
>>>
>>> I've captured the last few lines from my screen output and included as
>>> an attachment. I don't know if the fault is Vim or my Cygwin environment
>>> which I update regularly.
>>> Has anybody else experienced this problem? I have been building Vim for
>>> console mode and the GUI version for years and failed compilations have
>>> rarely occurred.
>>>
>>> I'm working on a Windows 7 box with the latest Cygwin (x86) environment
>>> installed. I'm running with all of the latest upgrades and security
>>> upgrades.
>>>
>>> v/r,
>>> Greg
>>>
>> There seems to be a conflict between Cygwin headers and Vim headers.
>> Could you paste lines 4951 and 5090 of /usr/include/w32api/winnt.h (as
>> seen from Cygwin bash) into a reply email please?
>>
>>
>> Best regards,
>> Tony.
> Hope this is what you're looking for.
>
> Thanks, Greg
>
In my Vim for GTK2/Gnome2, cscope finds the Status identifier as follows:
- defined by typedef at
/usr/include/X11/SM/SMlib.h line 168
/usr/include/X11/SM/SMlib.h line 306
/usr/include/X11/ICE/ICElib.h line 163
- defined by #define at
/usr/include/X11/Xlib.h line 87
/usr/include/X11/ICE/ICElib.h line 36
- used 77 times; the Vim sources among them (as opposed to system
include files) are:
src/gui_x11.c line 775
src/if_xcmdsrv.c line 266
src/os_unix.c line 1858
src/os_unix.c line 1923

In all cases (and also in system include files) I see that identifier
used as a type, which conflicts with its use as a data-name in your
/usr/include/w32api/winnt.h which is indirectly included by the line

# include <windows.h>

at line 86 of src/mbyte.c and within the range of an #ifdef WIN32UNIX.
The only #include earlier in the same source file is for "vim.h" with
quotes.

Bram, do you think we _can_ avoid this conflict, considering that the
conflicting definitions are both in system include files?


Best regards,
Tony.
--
There once was a girl from Madras
Who had such a beautiful ass --
It was not round and pink
(As you bastards think)
But had two ears, a tail, and ate grass.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.