Mercurial > pidgin
annotate README.mingw @ 15786:b25acae693cd
Change connection.c:gaim_connection_error() to still work even if the
message parameter is NULL. There's no reason to error-out of that
function just because some yuppie didn't pass us an error message.
But we still log a critical message, so those of you at home running
with fatal_criticals will still crash.
I noticed this because Jabber isn't handling <stream:error/> correctly
right now. Anyone else notice this? The code is written to look for
"stream:error", but our xmlnode stuff just sees "error" (even though
the "stream:error" format is sent over the wire). I think it's
because of the libxml change.
To reproduce the problem, sign onto the same resource twice and note
that the error message that Gaim gives you sucks.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Tue, 13 Mar 2007 07:33:08 +0000 |
parents | 5d03b309b482 |
children | ded8da3de5f8 |
rev | line source |
---|---|
14576
5d03b309b482
[gaim-migrate @ 17300]
Daniel Atallah <daniel.atallah@gmail.com>
parents:
4904
diff
changeset
|
1 How to build Gaim using MinGW |
3630 | 2 ============================= |
3 | |
14576
5d03b309b482
[gaim-migrate @ 17300]
Daniel Atallah <daniel.atallah@gmail.com>
parents:
4904
diff
changeset
|
4 Since these instructions are constantly changing, please refer to: |
3630 | 5 |
14576
5d03b309b482
[gaim-migrate @ 17300]
Daniel Atallah <daniel.atallah@gmail.com>
parents:
4904
diff
changeset
|
6 http://gaim.sourceforge.net/win32/build.php |