X-Spam-Check-By: sourceware.org Date: Fri, 1 Dec 2006 14:57:59 +0100 From: Ralf Wildenhues To: autoconf-patches AT gnu DOT org Cc: cygwin AT cygwin DOT com Subject: Re: cygwin -mno-cygwin AC_CHECK_SIZEOF Message-ID: <20061201135759.GE27847@iam.uni-bonn.de> Mail-Followup-To: autoconf-patches AT gnu DOT org, cygwin AT cygwin DOT com References: <20061201023212 DOT GH19404 AT cox DOT net> <456FA8DD DOT 3030409 AT byu DOT net> <20061201122805 DOT GK19404 AT cox DOT net> <4570316E DOT 5000109 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4570316E.5000109@byu.net> User-Agent: Mutt/1.5.13 (2006-11-01) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com * Eric Blake wrote on Fri, Dec 01, 2006 at 02:43:10PM CET: > According to Bob Rossi on 12/1/2006 5:28 AM: > > > > I really think this is the current best solution, that is, to modify > > autoconf to not use cat. Either that, or simply don't put the \n in the > > AC_CHECK_SIZEOF macro. I'm not sure why that is done in the first place. > > Avoiding the troublesome line ending seems best to me. How does this mesh with or formulated differently, if we're going to break POSIX compatibility, do we at least have sufficient evidence that all known systems cope with it? FWIW, the patch in that thread undid a previous change that removed the line ending. (I vaguely remember assuming some issues in Libtool with passing things without a newline; alas, I never got to the bottom of that, and forgot about the details since.) Cheers, Ralf > 2006-12-01 Eric Blake > > * lib/autoconf/c.m4 (AC_LANG_INT_SAVE): Avoid newline, to aid in > cross-compiling from cygwin to mingw. > Reported by Bob Rossi. -- 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/