Hello,
autoconf 2.63 has worked well for our project (icu), except for an
issue with a bare carriage return (hereafter '^M') in status.m4 which
shows up in resulting configure scripts. The line in question is:
ac_cr='^M'
If I am not misreading the git repository, the current development
ve
On Mon, 27 Oct 2008, Steven R. Loomis wrote:
Hello,
autoconf 2.63 has worked well for our project (icu), except for an issue
with a bare carriage return (hereafter '^M') in status.m4 which shows up in
resulting configure scripts. The line in question is:
ac_cr='^M'
If I am not misreading t
Thomas,
Sorry if I was unclear. I am using "^M" here to represent the single
byte with an ASCII value 0x0D / 13 decimal, carriage return. I was not
referring to the escape sequence "^" plus "M".
status.m4, and thus resulting 'configure' scripts, contain that byte,
even though all lines are
On Mon, 27 Oct 2008, Steven R. Loomis wrote:
Thomas,
Sorry if I was unclear. I am using "^M" here to represent the single byte
with an ASCII value 0x0D / 13 decimal, carriage return. I was not referring
to the escape sequence "^" plus "M".
This is what I was suggesting (something to consi
That works only on ASCII based platforms, and it requires tr (which
wasn't formerly required, according to the thread quoted below).
-s
Thomas Dickey wrote:
On Mon, 27 Oct 2008, Steven R. Loomis wrote:
Thomas,
Sorry if I was unclear. I am using "^M" here to represent the single
byte with a
Hi Eric,
* Eric Blake wrote on Mon, Oct 27, 2008 at 07:22:37PM CET:
> So, even though config.status has code in place to check for a broken
> lineno, the check passes rather than fails, because it doesn't contain
> instances of $LINENO any more; also, error messages printed on behalf
> of config.s
[Please don't top-post]
Steven R. Loomis icu-project.org> writes:
>
> That works only on ASCII based platforms, and it requires tr (which
> wasn't formerly required, according to the thread quoted below).
Autoconf is already a significant client of tr (for example, look at the output
of AC_C
Hi,
I want to place a rule in several Makefiles. So I thought about putting
@DESKTOP_DATA_RULE@
into every Makefile.am and define the rule via configure.ac. However, I
can't get it to work. The rule is:
$(desktop_DATA): $(desktop_in_files:.desktop.in=.desktop)
@list='$<'; for p in $$lis
Eric Blake wrote:
Steven R. Loomis icu-project.org> writes:
That works only on ASCII based platforms, and it requires tr (which
wasn't formerly required, according to the thread quoted below).
Autoconf is already a significant client of tr (for example, look at the output
of AC_CHECK
Daniel Leidert wrote:
Hi,
I want to place a rule in several Makefiles. So I thought about putting
@DESKTOP_DATA_RULE@
into every Makefile.am and define the rule via configure.ac. However, I
can't get it to work. The rule is:
$(desktop_DATA): $(desktop_in_files:.desktop.in=.desktop)
@l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom Browder on 10/26/2008 5:38 PM:
> That sounds like a good thing to me! Somehow I was able to get
> autoconf (2.61) to use bash functions in my configure.ac. Was that a
> lucky thing somehow?
>
> Any chance of getting (autoconf < conf
On Mon, 27 Oct 2008, Eric Blake wrote:
Autoconf already uses perl to convert configure.ac into configure. I
think you are asking what it would take to rewrite configure to use perl
rather than sh. But what would it buy us? sh is more portable than perl
(as measured by the number of platforms
Hi Daniel,
* Daniel Leidert wrote on Mon, Oct 27, 2008 at 11:04:34PM CET:
>
> I want to place a rule in several Makefiles. So I thought about putting
>
> @DESKTOP_DATA_RULE@
>
> into every Makefile.am and define the rule via configure.ac. However, I
> can't get it to work.
Should be possible w
13 matches
Mail list logo
