From: cgf AT bbc DOT com (Christopher Faylor) Subject: Re: Changing dll name -> cygwinb19.dll 6 Feb 1998 06:54:29 -0800 Message-ID: References: <199802060328 DOT TAA24021 AT rtl DOT cygnus DOT com> Reply-To: cygwin32-developers AT cygnus DOT com To: cygwin32-developers AT cygnus DOT com In article <199802060328 DOT TAA24021 AT rtl DOT cygnus DOT com>, Geoffrey Noer wrote: >As planned, we're changing the name of cygwin.dll to cygwinb19.dll >for the beta 19 release so it cannot interfere with other releases >using the dll. > >I will commit this change soon. Since I can make incompatible changes >while I'm doing this, I'm taking the opportunity to remove the >following from cygwin.din: > > set_new_handler -- a libgcc.a export which shouldn't be there > > cygwin_set_attributes -- a function stub from syscalls.cc > that just returns zero. I still don't know what this > was once for > >Let me know if there are any other changes I should do at this time. Do these need to be exported? _strace_wm (if so shouldn't it be cygwin32_strace?) __vc__10pinfo_listi __cygwin32_stack_trace __cygwin32__exception_handler How about exporting lock_pinfo and unlock_pinfo so ps.cc can use it? Then it can lock the process table while it is scanning it and theoretically avoid some occasional weird output. I've done this in my version, actually, prefixing the names with cygwin32_. -- http://www.bbc.com/ cgf AT bbc DOT com "Strange how unreal VMS=>UNIX Solutions Boston Business Computing the real can be."