Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-Id: <199908092310.SAA01849@mercury.xraylith.wisc.edu> To: John Reiser cc: cygwin@sourceware.cygnus.com Subject: Re: B20.1: "ld -r -T foo.lds foo.o" SIGSEGV In-Reply-To: Your message of "Mon, 09 Aug 1999 15:47:52 PDT." <37AF5A98.DA829525@teleport.com> Date: Mon, 09 Aug 1999 18:10:07 -0500 From: Mumit Khan John Reiser writes: > (cygwin b20.1 on WinNT 4.0 + SP3) > > When I use "ld -r -T foo.lds foo.o", I get a SIGSEGV from ld. > The bug is in ei386pe.c/gld_i386pe_after_parse() not checking > for 0==entry_symbol. A workaround, which may be needed later > anyway, is to define any global symbol as the entry point: > > ld -r -T foo.lds -e foo foo.o This has been fixed. 1999-06-12 Ian Lance Taylor * emultempl/pe.em (gld_${EMULATION_NAME}_after_parse): Don't add entry_symbol as an undefined symbol when doing a relocateable link. From . You may want to try a new binutils snapshot and see how it flies. For prebuilt binaries, see: ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/snapshots/ Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com