[Pidgin] #3096: msimprpl fails to build in Solaris 9, msdos line-ending related?

[Pidgin]

#3096: msimprpl fails to build in Solaris 9, msdos line-ending related?
------------------------+---------------------------------------------------
  Reporter:  dhalik     |       Owner:  dhalik  
      Type:  defect     |      Status:  new     
  Priority:  minor      |   Milestone:          
 Component:  libpurple  |     Version:  2.2.0   
Resolution:             |    Keywords:  msimprpl
   Pending:  0          |  
------------------------+---------------------------------------------------
Changes (by jeff):

  * keywords:  => msimprpl
  * owner:  jeff => dhalik
  * summary:  2.2.0 myspace protocol fails to build in Solaris 9 =>
              msimprpl fails to build in Solaris 9, msdos
              line-ending related?

Comment:

 Strange, the 'invalid whitespace character in directive' warnings are on
 lines like
 {{{
 #ifndef _MYSPACE_SESSION_H
 }}}
 Might be a line-ending problem. Try replacing all \r\n by \n in *.[ch], or
 vice versa. Your OS might come with tools named unix2dos or dos2unix to
 help do this. If not, try this:
 http://www.obviously.com/tech_tips/dos2unix.html . The MySpace plugin
 files have DOS line endings because I've been doing a lot of work while on
 Windows, but they really should have Unix line-endings. If using Unix line
 endings works, I'll update the next release of msimprpl to exclusively
 have Unix line endings.

 If that doesn't work, you could try applying this patch:
 http://msimprpl.darkthoughts.net/3096-zap-define-nonewline.patch (with
 `patch < 3096-zap-define-nonewline.patch` at the command-line), and
 pasting the output of the compilation here. Looks like the 'invalid source
 character' messages are from a multi-line macro, but this patch makes it
 all into one line.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/3096#comment:3>
Pidgin <http://pidgin.im>
Pidgin