tor/autogen.sh

#!/bin/sh

if [ -x "`which autoreconf 2>/dev/null`" ] ; then
  opt="-i -f -W all,error"

  for i in $@; do
    case "$i" in
      -v)
        opt="${opt} -v"
        ;;
    esac
  done

  exec autoreconf $opt
fi

set -e

# Run this to generate all the initial makefiles, etc.
aclocal -I m4 && \
	autoheader && \
	autoconf && \
	automake --add-missing --copy
./autogen.sh runs auto* and then ./configure It should be all you need to do to get working Makefiles on your platform, whatever your platform is. :) Let me know if it doesn't generate Makefiles for you. There will still be some bugs to work out in detecting openssl correctly, in checking for only the right header files, etc. But we're on our way. svn:r15 2002-06-29 05:01:49 +02:00			`#!/bin/sh`
Do not run configure from autogen.sh. Also switch to set -e instead of linking all the commands using && svn:r11158 2007-08-17 23:53:57 +02:00
Use autoreconf, not autoconf&&automake&&etc in autogen.sh The autoreconf tool deals much better with detecting which tools to use on your particular platform, handling cases where your install-sh script gets stable, and lots of other little tricky issues. We still fall back to autoconf&&automake&&etc in the case where "`which autoreconf 2>/dev/null`" says something we can't run. This is the first change of the 0.2.3.x series. 2010-09-27 17:20:12 +02:00			if [ -x "`which autoreconf 2>/dev/null`" ] ; then
Report errors when updating configuration files 2016-12-15 18:02:30 +01:00			`opt="-i -f -W all,error"`
Remove -v flag from autoreconf by default You can get it back by saying ./autogen.sh -v Patch from onizuka; for bug 4664. This isn't a complete fix, since starting from a clean checkout still reports that it's installing stuff 2013-01-19 00:00:51 +01:00
			`for i in $@; do`
			`case "$i" in`
			`-v)`
Report errors when updating configuration files 2016-12-15 18:02:30 +01:00			`opt="${opt} -v"`
Remove -v flag from autoreconf by default You can get it back by saying ./autogen.sh -v Patch from onizuka; for bug 4664. This isn't a complete fix, since starting from a clean checkout still reports that it's installing stuff 2013-01-19 00:00:51 +01:00			`;;`
			`esac`
			`done`

			`exec autoreconf $opt`
Use autoreconf, not autoconf&&automake&&etc in autogen.sh The autoreconf tool deals much better with detecting which tools to use on your particular platform, handling cases where your install-sh script gets stable, and lots of other little tricky issues. We still fall back to autoconf&&automake&&etc in the case where "`which autoreconf 2>/dev/null`" says something we can't run. This is the first change of the 0.2.3.x series. 2010-09-27 17:20:12 +02:00			`fi`

Do not run configure from autogen.sh. Also switch to set -e instead of linking all the commands using && svn:r11158 2007-08-17 23:53:57 +02:00			`set -e`

./autogen.sh runs auto* and then ./configure It should be all you need to do to get working Makefiles on your platform, whatever your platform is. :) Let me know if it doesn't generate Makefiles for you. There will still be some bugs to work out in detecting openssl correctly, in checking for only the right header files, etc. But we're on our way. svn:r15 2002-06-29 05:01:49 +02:00			`# Run this to generate all the initial makefiles, etc.`
Use a nicely written autoconf macro to determine the sign of a type This beats our old implementation, which wouldn't work when cross-compiling 2013-02-07 22:23:48 +01:00			`aclocal -I m4 && \`
r14641@catbus: nickm \| 2007-08-17 17:53:14 -0400 Stop running ./configure from autogen.sh. "Let's see if anybody complains!" says Roger. svn:r11159 2007-08-17 23:55:24 +02:00			`autoheader && \`
			`autoconf && \`
			`automake --add-missing --copy`