[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: build question

From: Eric Blake
Subject: Re: build question
Date: Sun, 10 Feb 2002 16:06:12 -0700

I take back this previous email.  Even with my patch below, I'm still
getting failures when trying to repeat my work:

$ cd ~/automake
$ perllibdir=./lib ./automake --libdir=lib --gnu bad macro name `--regex'

So my previous patch did not solve the file read problem, and it hurt
the file write problem as well ( was being generated with
some lines having \r\r\n, and perl's chomp only removes one of the two

I think what happened on my previous email is that I noticed that
configure had modified and various other files, inserting
\r's, so I had reverted those back to the CVS state before running `make
install'.  I am at a loss of good ideas to get rid of all those \r's,
short of mounting my cygwin directory in binmode before doing the CVS
update, or inserting some sort of hack like s/\r//g everywhere that
automake tries to read a line from a file.

Eric Blake wrote:
> News on Automake 1.5d on cygwin. I downloaded tag Release-1-5d (as
> opposed to the cvs head), and from my cygwin textmount, it wouldn't even
> configure without coaxing:
> $ make
> cd . && perllibdir=./lib /home/eblake/automake/aclocal --acdir=m4 -I
> /home/eblake/automake/m4
> cd . && \
>   perllibdir=./lib /home/eblake/automake/automake --libdir=lib --gnu
> Makefile
> bad macro name `--regex'
> make: *** [] Error 1
> Sure enough, line 33 had a trailing \, and the newly configured automake
> had misinterpreted the line continuation.
> However, on Tom Tromey's suggestion, I removed the call to binmode in
>, and everything worked fine for me.  I was able to run automake
> on files that previously died because of the CRLF nonsense of Windows.

This signature intentionally left boring.

Eric Blake             address@hidden
  BYU student, free software programmer

reply via email to

[Prev in Thread] Current Thread [Next in Thread]