Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3A8C378D.47862B19@yahoo.com> Date: Thu, 15 Feb 2001 15:09:49 -0500 From: Earnie Boyd Reply-To: Earnie Boyd X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: DJ Delorie CC: cygwin-developers AT cygwin DOT com Subject: Re: Exporting symbols from a .exe References: <20010215013211 DOT A2451 AT redhat DOT com> <200102151541 DOT KAA30990 AT envy DOT delorie DOT com> <20010215121332 DOT H3899 AT redhat DOT com> <200102151816 DOT NAA32134 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DJ Delorie wrote: > > > With MSVC you don't have to do anything special. If I try --shared, the > > executable just doesn't work. > > Right, because you just created a dll ;-) > > What I meant is that if you use the built-in mechanism to export > symbols, rather than dlltool, I suspect that ld will simply not bother > to check for symbols to export if you're not building a dll. IIRC, isn't -shared the default. What would happen if gcc -static were used instead? Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com