Am Donnerstag, 30. M=E4rz 2006 11:06 schrieb Hasso Tepper:
> Took my time and fought several hours with udev, hal, dbus, dbus-qt
> bindings, network manager etc. It's real challenge if your distro doesn't
> support all this stuff out of the box - all places full of hardcoded
> paths or configuretime paths, version hell (piece 0.x.y is incompatible
> with piece 0.x.y+1) etc. Finally it seemed to work, but ... even "make -f
> Makefile.cvs" in kdereview fails here:
> automake: cannot open < knetworkmanager/admin/ No such file or
> directory
> make[1]: *** [cvs] Error 1

That's what it was moved to kdereview for: to give people a chance to fix =

> After several attempts to manual Makefile edits, I finally got this:
> knetworkmanager-devicestore.cpp:101: error: no matching function for call
> to 'DeviceStoreDBus::updateNetwork(const QString&, const QString&, const
> char [1])'
> knetworkmanager-devicestore_dbus.h:52: note: candidates are: static void
> DeviceStoreDBus::updateNetwork(const char*, const char*, const char*,
> const char*)
> make[1]: *** [knetworkmanager-devicestore.lo] Error 1

That's most likely due to the NO_CAST defines in our SVN modules. Easy fix =

> Took NetworkManager-kde-0.1r5961-2.src.rpm from suse. Oh, it builds! But
> no luck with running. After short fight with dbus, knetworkmanager still
> says that "no network device found" and outputs to the terminal:
> updateNetwork: Found network without device? Bailing out.

Yeah, Networkmanager is pretty picky. Does nm-tool list devices?

Greetings, Stephan

>> Visit to unsubscrib=

e <<