Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <014201c31a41$8d0aaf70$6400a8c0@FoxtrotTech0001> From: "Bill C. Riemers" To: References: <016e01c319b3$8aad00e0$6400a8c0 AT FoxtrotTech0001> <20030514030950 DOT GE31224 AT redhat DOT com> Subject: Re: Help cross compiling for MingW32 standalone executables. Date: Wed, 14 May 2003 13:52:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > I was wondering if you knew something I didn't. :-) I didn't remember > any solution to this problem but with my aging brain that is > unsurprising. > > IIRC, the real problem here was in binutils. There was no way to get ld > to stop searching /usr/lib. I do not believe this is the real problem. If it was, then the configure script would also find libjpeg.a from /usr/lib .... The only library it finds that it shouldn't is libm.a. While I believe creating an empty libm.a would solve this particular problem, doing that inside the an autoconf macro is definitely the wrong place for that solution. Especially, since this might break the build if later the bug is fixed in mingw, or a libm.a is added as part of mingw. If that type of hack is neccissary it should be done in the gcc-mingw postinstall script. For a configure script it looks like I can change AC_CHECK_LIB(m,sqrt) to: AC_CHECK_LIB(msvcrt,sqrt,AC_CHECK_LIB(msvcp60,mbrlen),AC_CHECK_LIB(m,sqrt)) I can both avoid the problem of bogus libm.a detection, and avoid using msvcp60 under cygwin builds. The only problem remaining, is I'm not certain if I should use msvcrt, msvcrt20 or msvcrt40, since I do not know what the difference is between these libraries. Bill -- 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/