[Top][All Lists]

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

Re: Line endings on Windows with libtool.m4

From: Ralf Wildenhues
Subject: Re: Line endings on Windows with libtool.m4
Date: Thu, 4 Sep 2008 08:17:05 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hello Tom,

* Tom Bramer wrote on Thu, Sep 04, 2008 at 04:13:52AM CEST:
> I found an issue which I believe to be a bug, relating to line endings  
> on Windows (like there hasn't been anything like this before).

> During the detection of compiler-added object files and libraries (for  
> the runtime), libtool fails to detect an object in the compiler/linker  
> verbose output if :
> 1.) The system is Windows (of course).
> 2.) The object in the output is the last token in the output.
> This seems to be because there is a trailing '\015' character in the  
> last token, as it's the end of a line, which is terminated with CRLF in  
> this case.  The pattern *.o (*.$objext) will not match such arguments,  
> causing it to be ignored.

Thanks a lot for the bug report.  Looks like an issue.  Can you please
retry with Libtool 2.2.4 (there has been a small fix in the area, dunno
if that fixes your issue)?  If it doesn't, then please do the following
for me: wrap the problematic code section in configure in
  set -x
  set +x

then run configure, capture stdout and stderr in a file and post that
file as a gzip'ed attachment (so that line endings are unharmed by MTA)?

Other really cool thing would be a small example test that reproduces
the failure (which we could put in our testsuite later).  If that's too
much work, then we'd appreciate a link to the package you've seen this

BTW, in case you use MinGW also, does this happen there, too?


reply via email to

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