Hi,
--- Gerald Pfeifer gerald@pfeifer.com wrote:
Would you mind having a look? Thanks,
What version of gcc are you using? I don't get this warning. However, It will be gone shortly, all the conversion functions have been re-written (patches coming v. shortly). So I guess you can ignore this for now.
Cheers, Jon
===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
jon_p_griffiths@yahoo.com
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
On Sun, 5 Oct 2003, Jon Griffiths wrote:
What version of gcc are you using? I don't get this warning.
GCC 3.3 and also GCC 3.2.3 diagnoses the problem, IIRC. I strongly recommend to use one of these for Wine development, for they really catch a couple of (real) problems that older versions did not.
However, It will be gone shortly, all the conversion functions have been re-written (patches coming v. shortly).
Cool; yeah, let's wait then. OTOH:
"Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
;-)
Gerald
--- Gerald Pfeifer gerald@pfeifer.com wrote:
GCC 3.3 and also GCC 3.2.3 diagnoses the problem, IIRC. I strongly recommend to use one of these for Wine development, for they really catch a couple of (real) problems that older versions did not.
I'm on 3.2.2 and wasn't planning an upgrade any time soon (I recently upgraded my distro which was painful enough). Are your auto-build logs available somewhere for checking I haven't added any new warnings?
Cool; yeah, let's wait then. OTOH:
Your wish is my (shell) command - next crop of oleaut32 patches are sent and will hopefully remove those warnings.
Cheers, Jon
===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
jon_p_griffiths@yahoo.com
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
On Mon, 6 Oct 2003, Jon Griffiths wrote:
Are your auto-build logs available somewhere for checking I haven't added any new warnings?
That's an excellent suggestion! I made the last log available right away and hacked the script to automatically publish logs from the daily builds from now on:
http://rtp.freebsd.org/~gerald/
Would you find it useful to have a summary of all warnings at the top of every log?
Your wish is my (shell) command - next crop of oleaut32 patches are sent and will hopefully remove those warnings.
Thanks! :-)
Gerald
Hi,
--- Gerald Pfeifer gerald@pfeifer.com wrote:
That's an excellent suggestion! I made the last log available right away and hacked the script to automatically publish logs from the daily builds from now on: http://rtp.freebsd.org/~gerald/
Great stuff, cheers! The output format is fine, but would it be possible to rebuild the whole tree each night? that way any warnings will be present in every log, not just the one day that the change was committed.
Cheers, Jon
===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
jon_p_griffiths@yahoo.com
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
On Fri, 10 Oct 2003, Jon Griffiths wrote:
Great stuff, cheers! The output format is fine, but would it be possible to rebuild the whole tree each night?
In fact the whole tree is rebuilt each night, but this was not really clear from the log. If you check last nights log, you will see the following additional lines:
### make distclean ### cvs update : ### Using CC=/usr/bin/gcc ### ./configure ### make depend ; make
:-)
that way any warnings will be present in every log, not just the one day that the change was committed.
And, also new, at the end of each log you will find a new section like the following:
### Warnings config.c:172: warning: right shift count >= width of type config.c:178: warning: right shift count >= width of type /home/gerald/wine/tools/winegcc/winewrap.c:346: warning: tempnam() possibly used unsafely; consider using mkstemp() directx.c:852: warning: implicit declaration of function `glXGetProcAddressARB' drawprim.c:829: warning: implicit declaration of function `glMultiTexCoord4fARB' :
I hope this is useful?
Gerald
--- Gerald Pfeifer gerald@pfeifer.com wrote:
I hope this is useful?
Brilliant, thanks a lot!
Jon
===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
jon_p_griffiths@yahoo.com
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com