Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs
Date: Tue, 9 Dec 2003 15:59:36 -0600 (CST)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: Jaroslaw Pawlak <jpawlak AT zeus DOT polsl DOT gliwice DOT pl>
cc: cygwin AT cygwin DOT com
Subject: Re: problem with dll and stdout
In-Reply-To: <20031209221109.A4221@zeus.polsl.gliwice.pl>
Message-ID: <Pine.GSO.4.58.0312091553090.28297@eos>
References: <20031209221109 DOT A4221 AT zeus DOT polsl DOT gliwice DOT pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 9 Dec 2003, Jaroslaw Pawlak wrote:
> Brian Ford wrote:
> > On Tue, 9 Dec 2003, Jaroslaw Pawlak wrote:
> > > Hello! the problem is i'm not using all gcc but only ld and ld does
> > > not understands the -mno-cygwin switch.
> > >
> > It doesn't need to.
> >
> > If you are only using ld, then just don't link with cygwin1.dll or any
> > DLL's that depend on it.  That is what the -mno-cygwin switch would do.
> >
> Yes, but when i do that i see several error messges that something is
> missing, and i always get back to command with this dll... i'll try more
>
Then, please post those exact error messages so we can help :).

> > > Also i have to mix this cygwin dll with my VC program so this isn't
> > > good solution for me.  If you say that this option -mno-cygwin would
> > > help then please tell me something more about gcc.
> > >
> > So, you must be using Cygwin's gcc in regular Cygwin mode, and -mno-cygwin
> > would not be an option.  In that case, I think you are out of luck.
> >
> nonono, "cygwin dll" is not cygwin1.dll but dll that was compiled with
> cygwin :-) sorry for not to precise speech.
>
I understood that.  Was it compiled with -mno-cygwin?  If not, that is the
problem.  And if it can't be (because you have used Cygwin calls instead
of Windows native ones), see above.

> > I have "heard" there are complex work arounds for this, but they are not
> > 100% successful.  I don't know what they are, so plan to spend a lot of
> > time googling, head bashing, and examining your "inner self" if you
> > take this route. :)
> >
> > > I have changed ld becouse it had this 0 bit reloc bug, but when i
> > > tried to make my dll with gcc (i already got the *.obj so i used gcc
> > > olny for its -mno-cygwin switch) then i run into 0 bit reloc again.
> > >
> > Lobby the Cygwin binutils maintainer for an update, or make sure you have
> > replaced the ld gcc is using.  Look at the output of "gcc --verbose" to
> > see which one that is.
> >
> i'll do that...
> > > How to recompile the gcc alone?
> > >
> > You shouldn't need to if you do the above.
> >
> > > becouse binutils after compilation didn't left any gcc.exe.
> > >
> > It wouldn't.  gcc and binutils are separate software packages.
> >

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/