RE: [Tclxml-users] Problems building tclxml with expat on linux

[Andreas K. <and...@Ac...>]

> -----Original Message-----
> From: Forest W [mailto:lyr...@ti...]
> Sent: Tuesday, March 25, 2003 4:43 PM
> To: tcl...@li...
> Cc: Andreas Kupries
> Subject: Re: [Tclxml-users] Problems building tclxml with expat on linux
> 
> 
> >If I look at my Makefile.in I see
> >
> >	VPATH = 
> $(srcdir)/..:$(srcdir)/xmltok:$(srcdir)/xmlwf:$(srcdir)/xmlparse
> >
> >(in line 301) and the same is true for the generated Makefile. This is
> >different from what you are reporting.
> >
> >Do you have the leading / in your Makefile.in also ?
> >
> >If yes it is damaged, IMHO. If not we have a very weird 
> situation, because
> >the
> >transformation from Makefile.in to Makefile should leave the above line
> >alone.
> 
> No; expat/Makefile.in:301 sets VPATH to:
> $(srcdir)/..:$(srcdir)/xmltok:$(srcdir)/xmlwf:$(srcdir)/xmlparse
> As you can see, the leading $(srcdir) is present here.
> 
> The Makefile generated by configure sets VPATH to:
> /..:$(srcdir)/xmltok:$(srcdir)/xmlwf:$(srcdir)/xmlparse
> 
> However, when I delete the generated Makefile, run autoconf, and then
> run configure again, the new Makefile sets VPATH to:
> $(srcdir)/..:$(srcdir)/xmltok:$(srcdir)/xmlwf:$(srcdir)/xmlparse
> 
> What do you think of that?

What version of autoconf was used to create the configure in the CVS ?
What version of autoconf did you use ?

... Checking ... Here at ActiveState we regenerate most configure's via
our autoconf, which is 2.13 ... And tclxml/expat/configure is in the list.

In other words, we have never used the distributed configure.

It can be bad.

--
	Andreas Kupries <and...@Ac...>
	Developer @ http://www.ActiveState.com
	Join the community at the 10th Tcl conference http://wiki.tcl.tk/6274