Re: Help building dbus from 2.11-20050620.1710

I have managed to reproduce what you see by altering the configuration

What I did was enable the unit tests, 


which is not a good idea:
        [output from configure]
        NOTE: building with unit tests increases the size of the
        installed library and renders it insecure.
        NOTE: building with unit tests but without assertions means
        tests may not properly report failures (this configuration is
        only useful when doing something like profiling the tests)

I also made sure that the "--with-xml" configuration argument was set to


rather than

With these modifications, the glib tests fail to build because they are
*not* being linked against libexpat [hence the unsatisfied external

If you want to actually see these tests link you need to make sure that
-lexpat is in the link command.

How did you get to this point?

First, take a look at the configure statement at the top of


Is "--enable-tests" present? If it is, the question is "How did it get
there?" Looking at the configuration file, it is not a default unless
you are building in maintainer mode.

Do the following:
* cd ./bus/work/main.d/dbus-0.34

* cp config.log /tmp

* make -k distclean

* enter in the configure line from /tmp/config.log


and then run it.

* examine ./test/glib/Makefile
There should be lots of stuff commented out. 
For example:

        #noinst_PROGRAMS = test-dbus-glib$(EXEEXT) \
        #       test-service-glib$(EXEEXT) \
        #       $(am__EXEEXT_1)

* you can now run make and the problem you were experiencing should go

To insure that this can be done from the top:

* cd ./bootstrap/dbus
* make cookieclean
* edit the Makefile



to the end of the CONFIGURE_ARGS line to explicitly disable building the

* make install > make-install.log 2>&1 &


On Wed, 2005-06-22 at 16:29 +0100, Simon Morris wrote:
> On Wed, 2005-06-22 at 15:42 +0100, Joseph E. Sacco, Ph.D. wrote:
> > Simon,
> > 
> > I have been looking at the output that you posted to the list. The
> > output indicates that the failure occurs while
> > 
> >         ./tests/glib/test-dbus-glib
> > 
> > is being built. That's interesting because test-dbus-glib is not built
> > on my system when building dbus-0.34.
> > 
> > Questions:
> > * Why is test-dbus-glib being built?
> I'm afraid I have no idea :)
> > * Are you somehow working in "maintainer" mode?
> Not as far as I know. My first action is to 'make paranoid-install'
> inside desktop. These fun and games started when that failed on dbus
> with python bindings errors. 'make paranoid-install' in the bindings
> folder got me to this stage
> > * Did you do anything "interesting" to the dbus make file?
> > 
> No sir.
> ~sm
joseph_sacco [at] comcast [dot] net

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]