glabels: error: "Only <glib.h> can be included directly."

[fabio.zingaro@…]

Hi all,

I've problems on compiling gLables from ports, in the first step I obtain errors on references in glib libs. (attached main.log.1.txt)

With commands like this:

sudo perl -pi -w -e 's/#include <glib\/gi18n\.h>/#include <glib\.h>/g;' *.h

I substitute all references directly to a file in glib headers to glib.h

In the second step the build process goes forward but it stop for another error. (attached main.log.2.txt)

I've tried to compile with and without the +universal option but it prints the same error on unknown architecture x86_64.

Anyone could help me/us?

Thanks.

[fabio.zingaro@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to fabio.zingaro@…:

I've problems on compiling gLables from ports, in the first step I obtain errors on references in glib libs. (attached main.log.1.txt)

With commands like this:

sudo perl -pi -w -e 's/#include <glib\/gi18n\.h>/#include <glib\.h>/g;' *.h

I substitute all references directly to a file in glib headers to glib.h

I am able to reproduce the error "Only <glib.h> can be included directly" and have fixed it in the usual way in r99291.

In the second step the build process goes forward but it stop for another error. (attached main.log.2.txt)

I've tried to compile with and without the +universal option but it prints the same error on unknown architecture x86_64.

I'm not able to reproduce this second issue; it builds fine for me after the above fix. The log you attached for the second issue shows it was not a clean build attempt, so please wait 30 minutes, then "sudo port clean glabels" and "sudo port selfupdate" to get my changes from above, then try building again. If it fails again, then file a new ticket for the new problem and attach the new main.log file there. (We should keep it to one issue per ticket.)