Source code for something that won't compile has the line
#include <dbus/dbus.h> but in real life that header file is in
/usr/include/dbus-1.0/ Similar situation exists for the
Why doesn't Ubuntu provide a symlink
/usr/include/dbus pointing to the
dbus-1.0 directory? Is this an bug in the
dbus package? If intended, what it the purpose?
Is it a proper fix to add a symlink myself?
(Changing the source is not practical - there are many files, and they need to match what other people have.)
Ok, I totally misunderstood the situation, though it still comes down to a problem I think should be solved by a symlink. The dbus directory referred to in the
#include statement is a deeper level directory under
/usr/include/dbus-1.0/. The real problem is that the file
dbus-arch-deps.h appears to be missing, but is actually stored in the weird location
/usr/lib/x86_64-linux-gnu/dbus-1.0/include/dbus/ . So now, why doesn't Ubuntu provide a symlink to this in
/usr/include/dbus-1.0/dbus, or actually store it there?