"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.
> At some point earlier in this thread, it was mentioned that the
> auto* tools are not (yet) used for Xerces-C.
Yes, I believe they meant that 'the GNU tools are not (properly or
completely) used ...'. Having looked at the threads in the archives
from last year when Peter Koellner was working on this problem, it
seems that there is just a lot that ought to be done with
automake/autoconf that isn't.
http://marc.theaimsgroup.com/?l=xerces-c-dev&m=97158781207970&w=2
> By sure, autoconf is not used on the target system during
> runConfigure etc.
Once you have generated configure, there is no need to use autoconf,
and configure is definately used by runConfigure.
> Remains the possibility on the Xerces side, before creating the
> tarball. The configure script is part of the tarball - and it's in
> the CVS, isn't it? If you look into "configure", you will see a lot
> of comments which don't look at all like an output of autoconf, they
> are very special. So, at the most, it might be a semi-automatic
> process in the way that configure has been created from configure.in
> and then edited manually.
>
> >
> > Something will have to be modified in configure.in.
>
> I cannot find anything wrong in configure.in, the only relevant part there is
>
> AC_SUBST(prefix)
> prefix_include=${prefix}/include/xercesc
> AC_SUBST(prefix_include)
>
> and that seems to be in the correct order.
> So I still suppose someone has edited "configure" afterwards,
> breaking the default setting of prefix_include.
like my diff shows, I don't think that was done.
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
