X-Spam-Check-By: sourceware.org Message-ID: <4419C8A2.7F00601C@dessent.net> Date: Thu, 16 Mar 2006 12:20:50 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Don't understand proc magic check. References: <002b01c64922$4ab5ec30$a501a8c0 AT CAM DOT ARTIMI DOT COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dave Korn wrote: > I don't even understand how it can get to the "proc magic mismatch" error > without printing out the "res is ..." debugging message, and I'm kinda stumped > what to try next. Anyone got /any/ suggestions at all? By any chance are you trying to use the newly-built DLL with installed headers from 1.5.19 or some other version that is still older than the just-built DLL? I make it a point to do something like "make install-headers DESTDIR=/usr" whenever installing a newly-built cygwin1.dll that I intend to actually use. > [*] I may be mistaken in my belief that I need them, but that's beside the > point. I've never had any problems using the packaged version of binutils, it seems to work fine with the split .dbg file. The packaged version of binutils is what created the .dbg file in the build in the first place, so I would say it's safe to assume that it has that support. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/