Hi Yaakov, On Aug 12 07:40, Yaakov (Cygwin/X) wrote: > On Fri, 2011-08-12 at 07:09 -0500, Yaakov (Cygwin/X) wrote: > > On Tue, 2011-08-09 at 19:45 +0100, Dave Korn wrote: > > > Yaakov, how is this going? I see you haven't uploaded anything yet. > > > I'm > > > back and able to resume maintainership duties if everyone would like. > > > > That's good news, we were starting to be worried about you. > > > > I was just getting KDE 4.7 out the door while I was waiting for David to > > finish the deps. Here is what I was planning to release: > > > > http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/gcc4 > > > > Besides the version update to 4.5.3, there are several changes over the > > distro 4.5.0, including: > > > > * Linked against shared (instead of static) libintl. > > * Fix shared libgnat installation. > > * Fix Java NIO (patch may not be required with recent snapshots). > > * Pass --large-address-aware when, and --tsaware only when, linking > > EXEs. > > * libtool fixup script actually changes .la files. > > * Don't install GCC .la files so that the libtool fixup script will be > > less needed in the future. > > * Revise gcc4-java alternatives usage. > > > > We'll all be glad -- myself included -- for you to resume gcc > > development; I have only taken a cursory glance at 4.6.1 (and not even a > > glance at gccgo), and I have no idea where trunk is holding. If you've > > got time to package stable branches on top of that, fine, otherwise I > > could still handle the packaging side while you focus on development. > > Either way, I think we really need a 4.5.3-2 with at least that patchset > > out as soon as David can finish updating the deps. > > > > Let me know how you'd like to proceed. > > BTW, for those interested, I'm already working on updating the Fedora > Cygwin toolchain to match the recent binutils/gdb releases and add the > --large-address-aware patch, along with restoring cygwin-gcc-java for > F15.
There's a small glitch in the cross toolchain: $ i686-pc-cygwin-gcc foo.c -o foo $ ls foo* foo foo.c Since foo is a Cygwin executable, shouldn't gcc append .exe? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat