Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Mon, 23 Jul 2001 18:32:38 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: ld non-relocatable Message-ID: <20010723183238.A4427@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <00de01c1133a$23521f60$806410ac AT local> <00fd01c11340$d0a51900$806410ac AT local> <3B5C9578 DOT 4090601 AT ece DOT gatech DOT edu> <02c501c113c6$9d284940$806410ac AT local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <02c501c113c6$9d284940$806410ac@local>; from robert.collins@itdomain.com.au on Tue, Jul 24, 2001 at 08:27:08AM +1000 Should we move this discussion to binutils AT sources DOT redhat DOT com? cgf On Tue, Jul 24, 2001 at 08:27:08AM +1000, Robert Collins wrote: >----- Original Message ----- >From: "Charles Wilson" > > >> No good. The --no-relocate switch has exactly the same effect as >> 'objcopy -R .reloc': they both strip ONLY the relocation info and not >> the debugging stuff. However, when you do that, and try to run an >> executable, you get the following popup: >> >> The application or DLL is not a valid Windows image. >> Please check this against your installation diskette. > >Urgle. > >> There seems to be some tie between the debug info and the reloc stuff -- >> you need both or neither, it seems. Since 'strip -g' will remove the >> debugging info (but not symbols nor reloc), it is interesting that the >> following works: >> > > >Ah well, worth a crack Nigel. I looked at removing the generation of >relocation info in the pe-dll emulation code, but from what I could see no >objects would get copied into the output if I did that :]. So I need a >replacement set of copy-object logic that doesn't do relocation. > >> on my earlier experiments with MSVC/link's /fixed switch. The DLL's >> generated that way HAVE symbols. HAVE debug info. DON'T have relocs. >> But executables work. > >Yeah - at link time all things are possible. I'll drop this for now, and >when I have a chunk of time to do more than trivial hacks, I'll bring it up >on binutils and see what the correct approach is.