>   Tweaking out k3b, I probably wasted time looking for
> resmgr.h. I take it it's dead. However, I have another
> configure failure with hal-dbus that I need to know if it
> should be fixed or if that code is somewhere else now.
> Specifically, I have gotten k3b fully built except for the
> following:
> 
> K3b - Include libdvdread (Video DVD ripping) support:
> K3b -               
>                
>         yes
> 
> K3b - Resmgr support:         
>            
>    no
> 
> K3b - Compile HAL support         
>            no
> K3b -     You are missing the HAL >=
> 0.5 headers and libraries
> K3b -     or the DBus Qt bindings.
> <snip, all others 'yes'>
> 
> Good - your configure finished. Start make now
> 
>   What's with the HAL support failing? Should I just
> ignore the Resmgr failure?

I don't know about the Remsgr error. I don't think all distros use resmgr. Slackware doesn't. That particular warning probably is safe.

The hal error is caused by not finding the tqt version dbus headers. In the configure output:

checking for the HAL... headers /usr/include/hal  libraries /usr/lib
checking for DBus... headers /usr/include/dbus-1.0 /usr/lib/dbus-1.0/include  libraries /usr/lib
checking for DBus-TQt bindings... searched but not found
Found HAL storage version 5

The configure process is finding libhal.h but not finding ${PREFIX}/include/dbus-1.0/.

Yesterday I discovered the same problem with kmplayer. With kmplayer I can cheat by adding --with-extra-includes=${PREFIX}/include/dbus-1.0/ but that does not work with k3b.

Seems both packages find the distro's copy of dbus-1.0 (installed in /usr/include) but won't look in $PREFIX for the TQt version that is built for Trinity.

I filed bug report 942 against k3b.

Darrell