Re: [agtk-devel] Problems building sources

[Haejoong L. <hae...@un...>]

> > P.S.  Do you still have precision problem with AIF loader?  Please
> > let me know.
> 
> That's working ok now. 

That's great news.

> I managed to build AGLIB again after having problems with telling it where 
> xercesc was, for some reason your configure.in script which tries to find the 
> version of the library (a neat method btw which shouldn't be necessary) 
> wasn't working, even though the test program was ok and output the right 
> version number.  In the end I hacked configure.in to add a 
> --with-xercesc-version arg but wasn't able to modify the script to not run 
> your check if this arg was supplied (I tried but the configure script just 
> crashed). Here's the lines I added, perhaps you can work them in more 
> successfully:
> 
> 
> AC_ARG_WITH(xercesc_version,
>   [  --with-xercesc-version=N_N_N  version number of libxerces-c, eg 1_7_0],
>   XERCESC_VER=xerces-c$withval)

Okay.  It wasn't working.  How it wasn't working?  What was the
configuration options you used?  What was the error message you had?
Do you keep, by any chance, the config.log file that was created
when it wasn't working?  How is your xercesc library installed; what
is the location of xercesc include files and what is the location of
xercesc libraries?  Would it be possible for you to give a procedure
with which I can reproduce the error?

Isn't it good thing to have a smart configuration script?  Can we
first try to fix the problem instead of throwing it away without
knowing the reason why it didn't work?

> I also note that you need to make clean after reconfiguring etc. to ensure 
> that all libraries get updated. On my first build the ag_tcl.so library 
> didn't get rebuilt.  I guess that this is just good practice but could be the 
> cause of some errors.  I wonder if automake can force this?

I haven't found a way to do that.  Usually it's a good habit to make
things clean when you compile ANY source packages.  Sometimes "make
clean" is not enough.  I prefer "make distclean" when I'm not sure
about the behaviour of the configuration script of source packages.
It cleans even makefiles, so I need to configure the package again
after that.  That's a good way to avoid mysterious errors, although
it takes time.

Haejoong