Re: [agtk-devel] Problems building sources

[Steve C. <ste...@mq...>]

On Tue, 12 Mar 2002 18:20, you wrote:
>
>
> 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?

The problem was that although xerces_ver was building properly and when I ran 
it by hand it gave the right output (1_7_0) the variable XERCESC_VER wasn't 
getting set properly (it got xerces-c instead of xerces-c1_7_0).  I don't 
understand why this was happening since the script looks good and I'm sure 
has worked ok for others (and probably for me at other times).  

My xercesc is installed as normal in /usr/local, the test program you 
generate worked ok and gave the right output, the problem seems to be getting 
that output into the shell script variable.

I didn't have time to work on reproducing the error, as it was I spent most 
of yesterday getting xerces-c to compile cleanly (another configuration 
nightmare) on two different machines in order to get the new AG code to 
build. 

> 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 wasn't trying to throw it away, I tried to wrap your test in an if..then 
but it produced a configure script that crashed, my shell scripting isn't the 
best so I thought I'd contribute what I had managed to get working in case it 
was useful.  If you can put the if..then around your test based on the 
--with-xerces-ver option then perhaps we'll have a workaround for cases when 
your test doesn't work.  

Steve