delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1996/11/12/20:00:46

From: bala AT viman DOT com (Bala Parthasarathy)
Subject: NT cannot recognize gnuwin32 executable
12 Nov 1996 20:00:46 -0800 :
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <328916F8.1047.cygnus.gnu-win32@viman.com>
Mime-Version: 1.0
X-Mailer: Mozilla 3.0 (X11; I; HP-UX A.09.05 9000/712)
Original-To: gnu-win32 AT cygnus DOT com
Original-Cc: bala AT viman DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

I recently downloaded beta 16 of gnu-win32 on my NT 3.51 server
and I've compiled a bunch of my Unix programs under gnu win32.
Many of them work fine, but some of them give an error
"Not a valid Windows NT application" error when I launch
them.

I compiled all of these using commands of the format:
gcc -o <name.exe> <obj1.0> <obj2.o>... mylib1.a mylib2.a -lstdc++ -lm

All my programs do use static libraries which I again create 
using gcc. From what I can tell the only difference between the 
programs which do work and those that don't is that the ones that don't
work are larger than the ones that do. When I compiled the objects with
-g option, the sizes of the ones that don't work are >1Mb and
when I compile without -g, they range from 500k to 1.1Mb.

Does anyone have a clue on what could be going on? Is there a
magic flag to gcc that I must be passing in? ANY input would be
greatly appreciated.

I'm not attaching the od -x output (or any other info you need) but 
I can send it to anyone who can help.

Thanks a lot,

Bala
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019