| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
svn path=/trunk/; revision=15187
|
|
Add svn:eol-style native
Add svn:keywords Id
svn path=/trunk/; revision=15180
|
|
they have LF at the end of the line on UN*X and CR/LF on Windows;
hopefully this means that if a CR/LF version is checked in on Windows,
the CRs will be stripped so that they show up only when checked out on
Windows, not on UN*X.
svn path=/trunk/; revision=11400
|
|
svn path=/trunk/; revision=11301
|
|
Automake newer than 1.4 survives if it finds more than one file for the
same package.
svn path=/trunk/; revision=10298
|
|
svn path=/trunk/; revision=6977
|
|
string to be echoed; use "tr" to delete new lines and, while we're at
it, also delete carriage returns (just in case this is being run under
Cygwin or something such as that, and it produces lines ending with
CR-LF). Don't use character classes - I seem to remember that some
versions of "tr" require you to put the classes in square brackets and
some other versions don't work if you put them in square brackets.
svn path=/trunk/; revision=6973
|
|
- Fix handling of aclocal include flags for aclocal-include
autogen.sh:
- Name version variables individually
- Disable configure at end of autogen.sh
svn path=/trunk/; revision=6965
|
|
svn path=/trunk/; revision=4886
|
|
svn path=/trunk/; revision=4885
|
|
If GTK+ is not detected, then ethereal is not built.
svn path=/trunk/; revision=2695
|
|
1) aclocal expects autoconf/automake macros to be hidden;
2) GTK+ hid its autoconf/automake macros;
and, if both places exist but aren't the same directory, returns a "-I"
flag to tell aclocal to look in GTK+'s directory.
Then have "autogen.sh", and Makefiles in directories with "acinclude.m4"
files, use that script and pass what flag it supplies, if any, to
aclocal.
This should, I hope, avoid problems such as those FreeBSD systems where
GTK+ was installed from a port or package (and thus stuck its macros in
"/usr/X11R6/share/aclocal") but aclocal doesn't look there.
(It doesn't solve the problem of somebody downloading and installing,
say, libtool from source - which means it probably shows up under
"/usr/local", with its macros in "/usr/local/share/aclocal" - on a
system that comes with aclocal (meaning it probably just looks in
"/usr/share/aclocal", but that may be best fixed by, whenever you
download a source tarball for something that's part of your OS,
configuring it to install in the standard system directories and
*overwriting* your OS's version.)
svn path=/trunk/; revision=2165
|
