[Mono-dev] Win32 build errors (recent change)
matthi.d at googlemail.com
Fri Jun 15 22:18:13 UTC 2012
I could be wrong but what I basically did was to disable the "warning as
This enables you to build the thing (at least I was able to build it)...
I did mention this because Rob wanted to build mono for windows and it
should be possible with the patch.
This is in no sense a solution to the problem (this is why i called it a
temporary patch) and should not be pushed,
sorry when it did sound like that.
Note though: the other patches that are included should be pushed as they
fix very basic errors (thats why I made them extra)
Hope this helps to clarify things.
Have a nice weekend,
On Fri, Jun 15, 2012 at 11:47 PM, Rob Wilkens <robwilkens at gmail.com> wrote:
> I would love to help with this, on some level, but i would have to submit
> patches via a patchfile rather than github because of the way my git fork
> is currently set up.... i'm not entirely sure of the patch creation
> process other than 'diff -urp' i think to create them, then patch -p1 (or
> similar) to apply them.
> Is there anything you'd like help with here? Should i hunt down header
> files so that we have functions with declarations rather than without, or
> add declarations to header files (existing or new) based on actual function
> parameters? I would probably focus on the ones that prevent compile rather
> than dealing with every possible warning.
> Also, my weekend's are rarely completely free - I'm usually more available
> during the week (tomorrow we're planning a walk in NYC, and the next day
> will probably spend most of day at sister's house).. If i started on it,
> tonight would probably be spent downloading from github and starting on a
> compile, i doubt i'd get that far.
> On 06/15/2012 05:32 PM, Jonathan Chambers wrote:
> I see patches that you submitted, but I don't think they address the
> issue here which is warnings for functions without declarations. If you
> submitted patches for this, please provide a link.
> On Mon, Jun 11, 2012 at 11:57 PM, Matthias Dittrich <
> matthi.d at googlemail.com> wrote:
>> I did report that and I also included a (temporary) patch for this (and
>> possibly other) issue, to make it build successfully.
>> See one of my previous emails (I cant include a link or attachment right
>> now as I'm not at home).
>> Von: Robert Wilkens
>> Gesendet: 12.06.2012 05:49
>> An: Jonathan Chambers
>> Cc: mono-devel-list at lists.ximian.com
>> Betreff: Re: [Mono-dev] Win32 build errors (recent change)
>> Awesome, just was hoping it wasn't my end.
>> On Jun 11, 2012, at 11:44 PM, Jonathan Chambers wrote:
>> Certain warning have been made into errors as the warnings are not safe
>> on 64-bit builds. I am looking into fixing the build now.
>> On Mon, Jun 11, 2012 at 9:23 PM, Rob Wilkens <robwilkens at gmail.com>wrote:
>>> In my local copy of mono (robwilkens/mono on github) I can build in
>>> cygwin just fine...
>>> In the real mono/mono, i get the following error:
>>> In file included from ../../eglib/src/glib.h:7,
>>> from socket-io.c:20:
>>> /usr/i686-pc-mingw32/sys-root/mingw/include/stdio.h:536: warning: no
>>> previous prototype for 'fopen64'
>>> /usr/i686-pc-mingw32/sys-root/mingw/include/stdio.h:548: warning: no
>>> previous prototype for 'ftello64'
>>> socket-io.c: In function
>>> socket-io.c:835: warning: passing arg 3 of `ioctlsocket' from
>>> incompatible pointer type
>>> socket-io.c: In function
>>> socket-io.c:1278: error: implicit declaration of function `time'
>>> Has there been recent build changes to Win32 building?
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list