"Jason E. Stewart" wrote:
>
> "Michael Huedepohl" <[EMAIL PROTECTED]> writes:
>
> > "Jason E. Stewart" wrote:
> > >
> > > "Michael Huedepohl" <[EMAIL PROTECTED]> writes:
> > >
> > > > Well, I've analyzed the configure file and found a solution:
> > > > You only have to move the setting of prefix_include behind the check
> > > > `test "x$prefix" = xNONE && prefix=$ac_default_prefix'.
> > > > I.e., remove line 1289 and insert it after line 1376.
> > > > Here is the diff output:
> > > > diff -r1.4 configure
> > > > 1289d1288
> > > > < prefix_include=${prefix}/include/xercesc
> > > > 1376a1376
> > > > > prefix_include=${prefix}/include/xercesc
> > > >
> > > > Can you commit this change?
> > >
> > > No. Because configure is automatically generated from configure.in
> > > using autoconf. Any changes to configure will be lost the next time
> > > someone runs autoconf.
> >
> > Are you really sure?
>
> $ cp ./configure ./configure.bak
> $ autoconf
> $ diff ./configure ./configure.bak
> $
>
> Seems to be.
Okay, I had to step deeper into the autoconf mechanism.
Now I found a solution for configure.in, here is the diff
for configure.in:
66c66
< prefix_include=${prefix}/include/xercesc
---
> prefix_include='${PREFIX}/include/xercesc'
And here is the diff for configure (identical to the result of autoconf,
for systems without autoconf):
1289c1289
< prefix_include=${prefix}/include/xercesc
---
> prefix_include='${PREFIX}/include/xercesc'
I tested this with the default prefix setting and with the -P option
for runConfigure, and it worked.
Hope you can commit it now.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
