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 Message-ID: <71251C7D5FB1D2119C8F0008C7A44ED1037925F4@es07snlnt.sandia.gov> From: "Liang, James" To: "'Cygwin List'" Subject: RE: using shared libraries w/o cygwin Date: Wed, 10 Mar 2004 08:44:25 -0700 MIME-Version: 1.0 X-PMX-Version: 4.5.0.90627, Antispam-Core: 4.0.4.92622, Antispam-Data: 2004.3.9.93900 X-WSS-ID: 6C51E8511767647-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit My current goal is to run my custom build of objcopy WITH cygwin1.dll Is there a special compile or link time flag that tells it to link the cygwin1.dll instead of doing whatever it's doing now that's causing the crashes? > -----Original Message----- > From: Larry Hall [mailto:cygwin-lh AT cygwin DOT com] > Sent: Tuesday, March 09, 2004 7:59 PM > To: Liang, James; 'cygwin AT cygwin DOT com' > Subject: Re: using shared libraries w/o cygwin > > > At 07:35 PM 3/9/2004, you wrote: > >Hi. I've got a port of objcopy that I'd like to run on > Windows systems. > >I'd rather not have to install cygwin on the machine that > >I'm going to be running this tool on. > > > >The problem I'm having is that whenever I run my program on > a file, it > >appears to have a STACK_VIOLATION on a call to malloc. > >It works just fine under Linux, under cygwin, and can print the usage > >statement and things like that under "DOS", > >but crashes in DOS whenever I actually pass it a data file. > > > >So far, the only explanation I can come up with is that > there's some sort of > >failure during the dynamic libraries. Is there any way I can > >setup a DOS environment to make it run? I tried statically > linking in bfd, > >but that didn't seem to the problem either. Could this be caused > >by something else? > > > The 'objcopy' that comes with the 'binutils' package works fine when > invoked directly from a DOS prompt (outside of a Cygwin > shell). Of course, > that one comes with Cygwin and links to cygwin1.dll. If you > don't want > to have to install Cygwin or manage a local copy of > cygwin1.dll on your > target systems, then this isn't an option for you. However, > if you're > using a custom built version of 'objcopy' that doesn't use > cygwin1.dll, > then the question is really off-topic for this list. You'll need to > debug the problem yourself. Sorry. > > > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 838 Washington Street (508) 893-9889 - FAX > Holliston, MA 01746 > > -- 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/