Re: Some notes on building gcc-4.3.0

Shankar Unni wrote: > You already see the effects of this in the Linux world, with the more > recent distributions having to ship a set of compat_libgcc_blah packages > for each major (ABI-incompatible) previous release going back (they're > on 4.1/4.2 these days, and there's one for 3.3 and one f

Re: Some notes on building gcc-4.3.0

Brian Dessent wrote: Does this mean that we'll start to libgcc_s.dll's sprouting like mushrooms in the install dirs of various apps, or in *gasp* %WINDIR%/system32 over the coming years? Is this library versioned at all? What about conflicts? You already see the effects of this in the Linux

Re: Some notes on building gcc-4.3.0

Charles Wilson wrote: > > Are we really going to tell them that there is no choice in the matter, > > that if they want cross-.so EH they must suffer shared libraries? > > Yes. Microsoft does the same thing. They just have an inside advantage > in supplying their runtime with the OS. > > > The

Re: Some notes on building gcc-4.3.0

Brian Dessent wrote: Charles Wilson wrote: C++ exceptions across DLL boundaries [*] This also affects java. It is /NOT/ solved in 4.2, nor svn trunk. The Official Way Forward is to get shared runtimes working...which explains my patch-in-progress, above. For the MinGW community for sure

Re: Some notes on building gcc-4.3.0

Charles Wilson wrote: > C++ exceptions across DLL boundaries [*] > This also affects java. It is /NOT/ solved in 4.2, nor svn trunk. The > Official Way Forward is to get shared runtimes working...which explains > my patch-in-progress, above. For the MinGW community for sure, and for the Cyg

Re: Some notes on building gcc-4.3.0

Charles Wilson wrote: > So, I thought I'd post my experiences, which ultimately resulted in a > fully bootstrapped native cygwin compiler, with c,c++,objc,fortran,java > frontends. Many thanks for this, Charles. At this point, why not to post also the resulting binaries so that Cygwin people c

Re: Some notes on building gcc-4.3.0

Yaakov (Cygwin Ports) wrote: First, I had to massage the tree in the following ways (and I was using revision 125636): Out of curiosity, have you done this with cygport yet? No: it would impose too heavy a burden on my already overloaded plate. I'm using an alternate prefix (/opt) because I

Re: Some notes on building gcc-4.3.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Charles Wilson wrote: > I was testing Danny Smith's latest DWARF-2 patch, and building gcc from > the current (rather unsettled) trunk was a bit tricky. So, I thought > I'd post my experiences, which ultimately resulted in a fully > bootstrapped nat

Re: Some notes on building gcc-4.3.0

On Wed, 13 Jun 2007, Charles Wilson wrote: It'd be nice if the archiving software would Do What I Mean and Not What I Say. It inlined all the patches. So, here's a tarball... The patches did come through as text attachments, though... And you can get the whole message from the archives in m

Re: Some notes on building gcc-4.3.0

It'd be nice if the archiving software would Do What I Mean and Not What I Say. It inlined all the patches. So, here's a tarball... -- Chuck gcc-4.3.0-patches.tar.gz Description: GNU Zip compressed data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: