| Commit message (Collapse) | Author | Age |
|
|
|
| |
This beats our old implementation, which wouldn't work when cross-compiling
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
Stop running ./configure from autogen.sh. "Let's see if anybody complains!" says Roger.
svn:r11159
|
|
|
|
|
|
| |
linking all the commands using &&
svn:r11158
|
|
|
|
|
|
| |
break things much
svn:r10742
|
|
|
|
|
|
|
| |
Have autogen.sh script not run ./configure if NOCONF environment variable is set. This will make buildbot stuff go faster.
svn:r8656
|
|
|
|
| |
svn:r2635
|
|
|
|
|
|
| |
to build with it in the tarball
svn:r2163
|
|
|
|
| |
svn:r1369
|
|
|
|
| |
svn:r877
|
|
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
|