From: Pascal.Trouvin@integralis.co.uk Subject: Re[2]: Building-dll doc file 29 Jan 1997 10:11:06 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <01IES5STXU02003T8R.cygnus.gnu-win32@INTEGD.INTEGRALIS.CO.UK> Mime-Version: 1.0 Content-Type: TEXT/PLAIN Original-To: gnu-win32@cygnus.com, gunther.ebert@ixos-leipzig.de Original-Sender: owner-gnu-win32@cygnus.com LD still fails, but thank you very much Gunther. pascal ______________________________ Reply Separator _________________________________ Subject: Re: Building-dll doc file Author: gunther.ebert@ixos-leipzig.de at INTERNET Date: 28/01/1997 11:03 Pascal.Trouvin@integralis.co.uk wrote: > > Ooops, ok done. > > But now ld crashes : access_violation at C0...05 !!!!! > > It looks like an old problem with ld, but I do not remember if there > is any workaround. I've no idea why ld crashes but I forgot to tell you an important thing: The dll which would be created by your command lines would not work because there is no entry point specified. ld sets a default entry point in this case and it is nearly impossible to say what happens on dll startup (ok, it shouldn't have anything to do with the ld crash, but who knows ...) Please make sure that you have written a dll startup routine BOOL WINAPI dll_entry(HANDLE, DWORD, LPVOID) { return TRUE; /* if you don't have to do any dll initialization stuff this function just has to return TRUE */ } and tell the linker what the dll startup routine is: ld -e _dll_entry@12 Maybe this fixes your problem. Gunther ________________________________________________________ MIMEsweeper has scanned this message and its attachments and found it to be free of all known viruses. info@Integralis.com http://www.integralis.com Innovation, Integration, Integralis ________________________________________________________ - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".