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: <015801c319af$3c3763a0$6400a8c0@FoxtrotTech0001> From: "Bill C. Riemers" To: Subject: Re: Help cross compiling for MingW32 standalone executables. Date: Tue, 13 May 2003 20:23:26 -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 Here is a specific example: $ cat test.c #include #include int main() { void *s=sin; return (size_t)s; } $ gcc -mno-cygwin -o test.exe test.c -lm $ strings test.exe |grep dll msvcrt.dll cygwin1.dll KERNEL32.dll It turns out this example works fine, if I leave off -lm. If there is a flag I can set so a "configure" script will think -lm does not exist, my problem would be solved. Bill ----- Original Message ----- From: "Bill C. Riemers" To: Sent: Tuesday, May 13, 2003 7:35 PM Subject: Help cross compiling for MingW32 standalone executables. > 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 > -- 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/