Error compiling dbus for bluez-utils

Forum: Other Help Topics
Topic: Error compiling dbus for bluez-utils
started by: Juanito

Posted by Juanito on Feb. 09 2007,14:23

In an effort to reduce the size of bluez-utils, I decided to try and compile it from scratch rather than use apt-get from debian stable.

If I try and compile bluez-utils directly, ./configure complains that I need to install dbus first. If I try to compile dbus, ./configure complains that I need to install GNU gettext:

./configure --prefix=/usr
...
checking for msgfmt... no
./configure: line 27493: ./po/POTFILES.in: No such file or directory
configure: error:
*** You must have either have gettext support in your C library, or use the
*** GNU gettext library.

gettext-0.14 installs without any error messages - the problem is when I try to compile dbus, I get the same error message.

Does anybody have an idea if this is something to do with the gnu-utils package having been stripped of some files or do I need to enter a symlink to /po/POTFILES.in somehere (but where)?

Posted by ^thehatsrule^ on Feb. 09 2007,16:11

I assume you installed all with the prefix to /usr ?

If so, I'd try removing the dbus source directory, and re-extract a new one. Why? I'm not sure but I suppose sometimes something isn't correctly re-processed. Since *.in files usually indicate a file that's used by make, but usually created by the configure process, that's all I can think of right now.

If this doesn't work, maybe you need that "msgfmt" (message format?).

Posted by Juanito on Feb. 10 2007,05:29

..Sounded like a good idea, but unfortunately no joy.

msgfmt is apparently one of the utilities included with gettxt - I'll try a couple of versions of gettxt and see if that does it.

Edit
-----
gettxt-0.13 seemed to do the trick.

Now it complains something else is missing

Posted by ^thehatsrule^ on Feb. 10 2007,06:19

Heh, that just reminded me when I was compiling several different software bundles... this version would work here, some would even cause gcc to segfault, etc. - might have to do with restructuring of the APIs, or something.

In the end, I used the date of the 'target' software's release, and then searched for all the tools that were released before that date.

Just a tip that might help you out...

Posted by Juanito on Feb. 10 2007,07:51

I came to the same conclusion (date of releases) and bluez-utils finally compiled - I just need to go back and compile things cleanly and record the file names.

One thing I found was that compiling worked much better for me when I booted with the legacy boot code and used gnu-utils/gcc1-with-libs.dsl

Thanks for the help.