This is the mail archive of the
mailing list for the Cygwin project.
Re: Help cross compiling for MingW32 standalone executables.
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: "Bill C. Riemers" <cygwin at docbill dot net>
- Cc: cygwin at cygwin dot com
- Date: Tue, 13 May 2003 22:34:23 -0400 (EDT)
- Subject: Re: Help cross compiling for MingW32 standalone executables.
- Reply-to: cygwin at cygwin dot com
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 <http://cygwin.com/ml/cygwin/2003-05/msg00855.html>.
On Tue, 13 May 2003, Bill C. Riemers wrote:
> 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.
> ----- Original Message -----
> From: "Igor Pechtchanski" <email@example.com>
> To: "Bill C. Riemers" <firstname.lastname@example.org>
> Cc: <email@example.com>
> 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
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.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