OK, thanks. I've added the script you suggested originally. (It always
surprised me that there wasn't a single standard command line to do all
this stuff, and I'm glad to see that there is!)
On 11/21/2013 04:07 PM, Jason Gross wrote:
On my machine, your first autoreconf fails, but the second one runs
fine. autoreconf -fvi informs me that it calls:
aclocal --force -I m4
libtoolize --install --copy --force
autoconf --force
autoheader --force
automake --add-missing --copy --force-missing
(It also doesn't error like your autoreconf call.) The -i option will
also call autopoint, if it's deemed necessary.
On Thu, Nov 21, 2013 at 4:02 PM, Adam Chlipala <[email protected]
<mailto:[email protected]>> wrote:
On 11/21/2013 03:57 PM, Jason Gross wrote:
On Thu, Nov 21, 2013 at 3:45 PM, Adam Chlipala
<[email protected] <mailto:[email protected]>> wrote:
Also, the public Mercurial repository should now omit all
autogenerated files. It would be helpful to hear from people
who manage to build and install from fresh clones of that
repo, which lives at:
http://hg.impredicative.com/urweb
If you notice any autogenerated files that still appear in a
fresh clone, I'd be very glad to hear about them.
They all seem to be gone. However, I think it's standard
practice to include an executable "autogen.sh" file in the top
level directory which goes something along the lines of
#!/bin/sh
autoreconf -fvi
Ah, thanks, that makes sense. The invocation I use is:
autoreconf
libtoolize -cf
automake --add-missing --force-missing --copy
autoreconf
Does the one you're suggesting do the same things?
_______________________________________________
Ur mailing list
[email protected]
http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
