Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5023 - gtkmm, gtk, pango, sigc++ headers BROKEN

Attached to Project: Arch Linux
Opened by Jacco Gracy (Andares) - Wednesday, 12 July 2006, 01:42 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Many major headers are broken in the following way:
Take pango for instance.
Its headers are located in /usr/include/pango-1.0/pango.
There is no symlink for pango to /usr/include, #include <pango/foo.h> doesn't work while #include <pango-1.0/pango/foo.h> does.

Obviously, this cuses compile errors for many GUI applications, save the Qt ones.

In many of these libraries, /usr/lib/*-x.x/include/* isn't linked to /usr/include also.

I've observed this problem in the following libraries:
gtkmm
gtk
pango
pangomm
sigc++(1.0 and 2.0)
glade
gdk
gdkmm
glib
glibmm

The problem may be fixed by symlinking these libraries' inner directories and/or additional files, but _this may break things_.

A good way to find problem packages is to do:
[root@myhost include]# ls

...
libproblem-x.x
...

[root@myhost include]# cd libproblem-x.x && ls

Take note of the directories you see, then check for their existance in /usr/include.

Thanks for addressing this issue!
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 12 July 2006, 06:21 GMT
Reason for closing:  Not a bug
Additional comments about closing:  You have to set CFLAGS, see pkg-config --cflags pango for example. This is covered in most basic tutorials.

Loading...