gcc-3.1 issues warnings when specifying standard includes on the cmd-line; e.g: | $ gcc -I /usr/include -E - | cpp0: warning: changing search order for system directory "/usr/include" | cpp0: warning: as it has already been specified as a non-system directory Unfortunately, a *lot* of Hampton Beta 1 packages are setting such directives in their *-config scripts: | $ pkg-config oaf --cflags | -I/usr/include -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/orbit-1.0 ~~~~~~~~~~~~~~ As you can imagine, this will break -Werror builds (e.g. used while developing own projects). Since there are good reasons to warn about such bad '-I...', the affected packages must be fixed. I will use this report as a reference-point for bugs regarding this issue.
Why is this on gcc? Maybe we need a "general" component
OK, what's the status of this?
The packages affected by this bug and found by me are listed as an dependency. Three of them are fixed.
I'm planning to fix my packages but don't have an ETA.
Closing this tracking bug, as it's on a weird component and I'm not really using it to track (not dealing with these bugs as a group).