bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/17424] New: Does not build correctly with \r\n line terminators


From: m at rolle dot name
Subject: [Bug ld/17424] New: Does not build correctly with \r\n line terminators on Cygwin
Date: Mon, 22 Sep 2014 22:21:12 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=17424

            Bug ID: 17424
           Summary: Does not build correctly with \r\n line terminators on
                    Cygwin
           Product: binutils
           Version: 2.24
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: m at rolle dot name

Created attachment 7805
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7805&action=edit
Correct and incorrect generated ./ld/Makefile

I am building binutils from 2.24 source.  The Cygwin package has \r\n line
terminators, in the Windows style.
When I try './configure/ then 'make' in the source root, the build fails
compiling ld/ldemul.c.  The generated file ldemul-list.h was wrong, with some
garbage in the #define of EMULATION_LIST.  Sorry, lost the bad file after I
corrected other errors and did the build successfully.
I needed to remove the \r's in several scripts in order for them to execute
properly.  See Bug 17420.
What I needed to do to fix the problem with ldemul-list.h was to remove the
\r's from ./ld/configure-host.  The shell didn't complain about executing this
script, but it resulted in errors in the generated ./ld/Makefile, which in turn
resulted in the errors in ldemul-list.h.

I attach the good and bad versions of ./ld/Makefile.  You can see several major
diffs.

I would guess the only good way to fix this problem is to make the shell
somehow treat \r\n as the same as \n.  Now I thought that was a feature of text
files in unix (that is, the \n character represents whatever the system line
terminator is), so perhaps that's where the real problem is.  In Cygwin, some
text files will have \n terminators and others will have \r\n terminators, but
somehow these should logically look the same.

I will post a general Cygwin bug to refer to this one as an example.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



reply via email to

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