Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199911111713.LAA07043@mercury.xraylith.wisc.edu> To: Steve Jorgensen cc: John Fralinger , cygwin AT sourceware DOT cygnus DOT com Subject: Re: More Cygwin 1.0 CD In-Reply-To: Your message of "Thu, 11 Nov 1999 10:07:09 MST." <199911111707 DOT KAA11660 AT benson> Date: Thu, 11 Nov 1999 11:13:16 -0600 From: Mumit Khan Steve Jorgensen writes: > > dllwrap fails with the following after wading through the header file > > name changes from B20.1 to 1.0. What header name changes? Please elaborate. I wasn't aware of user visible headers that have changed names. > > I've never gotten dllwrap or the gcc set of instructions for > creating DLL's to work under B20.1 or 1.0.. I just figured it > was yet another stupid artifact of windows dll's.. I'm using > a combination calls to nm, dlltool, and ld to create dll, which > seems to be working for me. I can send you a perl script that > does the right sequence if you like. Please post. BTW, dllwrap does nothing more than your perl script, just that it handles a few defaults more intelligently. $ dllwrap --dry-run [....] shows exactly what it's going to do. The -v option shows the actual invocations. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com