[MacPorts] #35883: pidgin-encryption: #error "Only <glib.h> can be included directly." (was: pidgin-encryption fails building)

[MacPorts]

#35883: pidgin-encryption: #error "Only <glib.h> can be included directly."
--------------------------------------+-------------------------------------
 Reporter:  ailinca.marius@…          |       Owner:  ryandesign@…           
     Type:  defect                    |      Status:  assigned               
 Priority:  Normal                    |   Milestone:                         
Component:  ports                     |     Version:  2.1.2                  
 Keywords:                            |        Port:  pidgin-encryption      
--------------------------------------+-------------------------------------
Changes (by ryandesign@…):

  * status:  new => assigned
 * cc: rsync@… (added)
  * owner:  macports-tickets@… => ryandesign@…
  * port:  => pidgin-encryption


Old description:

> pidgin-encryption failes building with the message:
> "#error "Only <glib.h> can be included directly."
>
> Manually editing rsa_nss.c and modifiying:
> - #include "glib/gmain.h" to:
> + #include "glib.h"
> solves the issue.

New description:

 pidgin-encryption failes building with the message:
 {{{
 #error "Only <glib.h> can be included directly."
 }}}

 Manually editing rsa_nss.c and modifiying:
 {{{
 - #include "glib/gmain.h" to:
 + #include "glib.h"
 }}}
 solves the issue.

--

Comment:

 Yes this is the usual manifestation of glib 2.32+ incompatibility we've
 seen in many other ports already, and what you've suggested is basically
 the way it should be fixed.

 The script I usually use to fix these errors did not find anything to fix
 in pidgin-encryption, because this include is written improperly using
 "quotation marks" when system headers should be included with <angle
 brackets> instead.

-- 
Ticket URL: <https://trac.macports.org/ticket/35883#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS