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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 13 May 2003 22:34:23 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: "Bill C. Riemers" cc: cygwin AT cygwin DOT com Subject: Re: Help cross compiling for MingW32 standalone executables. In-Reply-To: <016e01c319b3$8aad00e0$6400a8c0@FoxtrotTech0001> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Bill, I thought this problem was fixed in more recent versions of gcc-mingw and cygwin, but apparently not. You should probably try the solution CGF provided in . Igor On Tue, 13 May 2003, Bill C. Riemers wrote: > Igor, > > You are right, I am using the -lm flag. However, you are wrong in that I am > not using an "older" version of cygwin. I just ran "setup" and all my > development packages are listed as "keep", meaning > they are the most current stable versions. For example: > > gcc is 3.2-3 > gcc-mingw is 20020817-5 > ... > > I've checked and my build does not like in cygwin1.dll if I edit the > Makefile's by hand to remove the -lm flag. The problem is the > "AC_CHECK_LIB(m,sqrt)" autoconf macro always report -lm exists and is needed > for the sqrt function when the host target is i686-pc-mingw32. So anybody > who tries to reproduce my build will have the same problem. > Bill > > ----- Original Message ----- > From: "Igor Pechtchanski" > To: "Bill C. Riemers" > Cc: > Sent: Tuesday, May 13, 2003 8:01 PM > Subject: Re: Help cross compiling for MingW32 standalone executables. > > > > On Tue, 13 May 2003, Bill C. Riemers wrote: > > > > > I've been attempting to build mingw32 standalone executables by > > > cross compiling with the -mno-cygwin option. I thought it was > > > working correctly, until I handed off the execuables to someone > > > without cygwin. It turns out the executables still link in > > > cygwin1.dll. Does anyone know what flag I should use to get a true > > > standalone excutable? > > > Bill > > > > "gcc -mno-cygwin" should work. If you had an older Cygwin, I'd've guessed > > you're linking with a "-lm" flag, but that should be fixed now. As it is, > > though, it's possible that you're explicitly linking one of the > > Cygwin-dependent DLLs. Try running "cygcheck yourapp.exe", and see what > > it depends on. That should tell you what you've linked in that's pulling > > in cygwin1.dll. > > > > If not, please provide the exact compile and link lines you're using to > > build your executable. > > Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Knowledge is an unending adventure at the edge of uncertainty. -- Leto II -- 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/