Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: <016e01c319b3$8aad00e0$6400a8c0@FoxtrotTech0001>
From: "Bill C. Riemers" <cygwin AT docbill DOT net>
To: <cygwin AT cygwin DOT com>
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0305131959230 DOT 17480-100000 AT slinky DOT cs DOT nyu DOT edu>
Subject: Re: Help cross compiling for MingW32 standalone executables.
Date: Tue, 13 May 2003 20:38:01 -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

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" <pechtcha AT cs DOT nyu DOT edu>
To: "Bill C. Riemers" <cygwin AT docbill DOT net>
Cc: <cygwin AT cygwin DOT 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
> -- 
> 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/