On 05/07/2013 04:05 PM, Jean-Marc Lasgouttes wrote:
Le 07/05/13 22:04, Jean-Marc Lasgouttes a écrit :
Richard, what about this for 2.0.x?
Yes, that's fine.
rh
On 05/07/2013 04:05 PM, Jean-Marc Lasgouttes wrote:
Le 07/05/13 22:04, Jean-Marc Lasgouttes a écrit :
Richard, what about this for 2.0.x?
Yes, that's fine.
rh
Richard, what about this for 2.0.x?
JMarc
for automake 1.13
---
autogen.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/autogen.sh b/autogen.sh
index 8b48960..8239558 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -16,12 +16,12 @@ test $automake_version != {
}
case $automake_version in
-*' '1.[8-9]*|*' '1.1
Richard, what about this for 2.0.x?
JMarc
d support for automake 1.13
---
autogen.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/autogen.sh b/autogen.sh
index 8b48960..8239558 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -16,12 +16,12 @@ test "$automake_version" != "" && {
}
case
Le 06/01/13 20:37, Stephan Witt a écrit :
This is the terminal output of automake:
Using automake (GNU automake) 1.13.1
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
configure.ac:180: warning: The 'AM_PROG_MKDIR_P' macro
Am 21.01.2013 um 12:21 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org:
Le 06/01/13 20:37, Stephan Witt a écrit :
This is the terminal output of automake:
Using automake (GNU automake) 1.13.1
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building
Le 06/01/13 20:37, Stephan Witt a écrit :
This is the terminal output of automake:
Using automake (GNU automake) 1.13.1
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
configure.ac:180: warning: The 'AM_PROG_MKDIR_P' macro
Am 21.01.2013 um 12:21 schrieb Jean-Marc Lasgouttes :
> Le 06/01/13 20:37, Stephan Witt a écrit :
>> This is the terminal output of automake:
>> Using automake (GNU automake) 1.13.1
>> Using autoconf (GNU Autoconf) 2.69
>> Building macros...
>> Building config header
Am 06.01.2013 um 20:37 schrieb Stephan Witt st.w...@gmx.net:
Is anyone using automake 1.13 already?
LyX's autogen.sh is ready for 1.12 only.
It's easy to change that. Is it desirable?
Somehow a shell script named test-driver in the config source directory is
introduced by running
Le 08/01/13 21:31, Stephan Witt a écrit :
Changing the macro mkdir_p to MKDIR_P would require automake 1.10 - but this is
used already anyway.
Therefor the check in autogen.sh is wrong? Or do I miss something?
We could finally get rid of the included gettext. Who would be impacted?
Am 06.01.2013 um 20:37 schrieb Stephan Witt <st.w...@gmx.net>:
> Is anyone using automake 1.13 already?
>
> LyX's autogen.sh is ready for 1.12 only.
It's easy to change that. Is it desirable?
> Somehow a shell script named test-driver in the config source directory is
>
Le 08/01/13 21:31, Stephan Witt a écrit :
Changing the macro mkdir_p to MKDIR_P would require automake 1.10 - but this is
used already anyway.
Therefor the check in autogen.sh is wrong? Or do I miss something?
We could finally get rid of the included gettext. Who would be impacted?
Is anyone using automake 1.13 already?
LyX's autogen.sh is ready for 1.12 only.
Somehow a shell script named test-driver in the config source directory is
introduced by running automake.
This is the terminal output of automake:
Using automake (GNU automake) 1.13.1
Using autoconf (GNU Autoconf
Is anyone using automake 1.13 already?
LyX's autogen.sh is ready for 1.12 only.
Somehow a shell script named test-driver in the config source directory is
introduced by running automake.
This is the terminal output of automake:
Using automake (GNU automake) 1.13.1
Using autoconf (GNU Autoconf
16 matches
Mail list logo