Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: ampersand at character 2048 in a command is lost in make To: cygwin@cygwin.com Message-ID: From: Jeremy Broughton Date: Tue, 16 Nov 2004 16:56:51 -0500 MIME-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=08BBE5DDDFE5BED38f9e8a93df938690918c08BBE5DDDFE5BED3" Content-Disposition: inline Note-from-DJ: This may be spam --0__=08BBE5DDDFE5BED38f9e8a93df938690918c08BBE5DDDFE5BED3 Content-type: text/plain; charset=US-ASCII Using cygwin 1.3.10 and 1.5.7, if an '&' ampersand character appears at character 2048 of a makefile command, the ampersand is lost from the command. If white-space is manipulated to move the & one character forward or backward in the makefile command, everything works fine. I have attached a testcase makefile below that reproduces the problem with simple makefile echo commands. Run "make fail" to see the failing case when an ampersand is at character 2048. Run "make ok1" and "make ok2" to see the same command succeed if the ampersand is shifted one character left or right respectively. Run "make ok3" to see the same command succeed if character 2048 appears in the middle of the echo command. (See attached file: makefile) Thanks. Jeremy Broughton e-mail: jeremyb@ca.ibm.com --0__=08BBE5DDDFE5BED38f9e8a93df938690918c08BBE5DDDFE5BED3 Content-type: application/octet-stream; name="makefile" Content-Disposition: attachment; filename="makefile" Content-transfer-encoding: base64 DQojIHRoaXMgaXMgMTAwOSBjaGFyYWN0ZXJzDQpCTEFIIDo9IGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxhaCBibGFoIGJsYWggYmxh aCBibGFoIGJsYWgNCg0KZmFpbCA6DQoJZWNobyAkKEJMQUgpICQoQkxBSCkg YmxhaCBibGFoIGJsYWggIDIwNDUgICYgZWNobyBPSw0KDQpvazEgOg0KCWVj aG8gJChCTEFIKSAkKEJMQUgpIGJsYWggYmxhaCBibGFoICAyMDQ1ICYgZWNo byBPSw0KDQpvazIgOg0KCWVjaG8gJChCTEFIKSAkKEJMQUgpIGJsYWggYmxh aCBibGFoICAyMDQ1ICAgJiBlY2hvIE9LDQoNCm9rMyA6DQoJZWNobyAkKEJM QUgpICQoQkxBSCkgYmxhaCBibGFoICAgICAyMDQ1ICYgZWNobyBPSw0KDQo= --0__=08BBE5DDDFE5BED38f9e8a93df938690918c08BBE5DDDFE5BED3 Content-Type: text/plain; charset=us-ascii -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ --0__=08BBE5DDDFE5BED38f9e8a93df938690918c08BBE5DDDFE5BED3--