Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe: <mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <199908041741.MAA04943@mercury.xraylith.wisc.edu>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: new snapshot -- fixes reported bugs?
Date: Wed, 04 Aug 1999 12:41:10 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

On Tue, 3 Aug 1999, Corinna Vinschen wrote:

> Mumit Khan wrote:
> > Yikes. I guess the new libgcc exception handling code includes one of
> > the Cygwin runtime headers, and you get a reference. This means that
> > -mno-cygwin is really hosed unless you get my mingw-extra package and
> > use the libgcc.a that's there.
> 
> This way, I could compile strace.

That had better! Otherwise, we'd be in serious trouble.

> 
> > You can also try -fno-exceptions -fno-rtti when building strace.exe and
> > see if that fixes it for now.
> 
> But this doesn't help.
> 

I didn't think it would, but worth a shot.

Any suggestions on how to handle this while building winsup without having
to multilib[1] gcc?

[1] multilibbing is a (painful) process which creates mulitiple runtime
libraries with varying characteristics. eg., a system that supports both
ELF and COFF needs two sets, a system that supports 32/64 bits two and
so on.

Regards,
Mumit