[lsb-bugs] [Bug 1845] include path warnings are too paranoid
bugzilla-daemon at linux-foundation.org
bugzilla-daemon at linux-foundation.org
Mon Dec 17 12:08:47 PST 2007
http://bugs.linuxbase.org/show_bug.cgi?id=1845
Mats Wichmann <mats at freestandards.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mats at freestandards.org
Status|NEW |ASSIGNED
--- Comment #1 from Mats Wichmann <mats at freestandards.org> 2007-12-17 12:08:46 ---
Here's a start:
/usr/include/libxml2
/usr/include/freetype2
/usr/include/gtk-2.0
/usr/include/glib-2.0
/usr/include/pango-1.0
/usr/include/atk-1.0
/usr/include/alsa
not clear if we think /usr/include/cups is a problem or not.
Probably, the Qt4 stuff is a problem if it turns up, I'm not sure it's
guaranteed to be in /usr/include/Qt*, as qt has had a strange history of
putting things in odd places. For example, many builds put qt3 headers in
/usr/lib{,64}/qt-3.3/include. I think one of the ideas with Qt4 was to clean
that mess up. However, it is multiple directories, and I don't know if the
lsbcc implementation could deal with a "wildcard".
On SuSE,
/opt/gnome/include/{atk-1.0,glib-2.0,gtk-2.0,pango-1.0}. We don't know why!
--
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the lsb-bugs
mailing list