X-Spam-Check-By: sourceware.org Message-ID: <456FAB30.4030303@highlandsun.com> Date: Thu, 30 Nov 2006 20:10:24 -0800 From: Howard Chu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061116 Netscape/7.2 (ax) Firefox/1.5 SeaMonkey/1.5a MIME-Version: 1.0 To: Eric Blake CC: autoconf AT gnu DOT org, cygwin AT cygwin DOT com, bob_rossi AT cox DOT net Subject: Re: cygwin -mno-cygwin AC_CHECK_SIZEOF References: <20061201023212 DOT GH19404 AT cox DOT net> <456FA8DD DOT 3030409 AT byu DOT net> In-Reply-To: <456FA8DD.3030409@byu.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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: >> What is the best way to resolve something like this? >> > > Perhaps experiment with a cygwin text mount, so that cygwin cat will > ignore the \r. Or experiment with the recent add-on to cygwin's bash, > where exporting SHELLOPTS with the cygwin-specific shell option igncr set > will tell subsequent /bin/sh invocations to strip \r from command > substitution. Or rather than trying to cross-compile, with mixed results > between mingw test binaries but cygwin build framework; just use the MSYS > environment so that your entire build process is native. > > Actually, maybe it would work if you invoked configure properly - since > - -mno-cygwin is requesting a cross-compiler, you REALLY should be invoking > it like this: > ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin \ > CC='gcc -mno-cygwin' > And the fact that you are now telling configure the truth that you are > cross-compiling, even though the cross binaries are executable, may be > enough for autoconf to try harder for discovering how AC_CHECK_SIZEOF > should behave without tripping up on line endings (and if that is not the > case, maybe we should consider patching autoconf to make it happen that way). > I was with you up to the end. You should have no expectation that anything compiled for the target can execute reasonably on the build host in a cross-compiling environment. As usual, I think just using MSYS is the best solution. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc OpenLDAP Core Team http://www.openldap.org/project/ -- 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/