From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: GCC dependencies (attn David Billinghurst)
Date: Sat, 13 Aug 2011 14:12:00 -0000 [thread overview]
Message-ID: <20110813141124.GE4098@calimero.vinschen.de> (raw)
In-Reply-To: <1313152852.7828.40.camel@YAAKOV04>
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
next prev parent reply other threads:[~2011-08-13 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 3:12 Yaakov (Cygwin/X)
2011-07-28 11:56 ` David Billinghurst
2011-07-29 23:37 ` Yaakov (Cygwin/X)
2011-07-30 0:26 ` Yaakov (Cygwin/X)
2011-08-09 18:45 ` Dave Korn
2011-08-09 21:46 ` David Billinghurst
2011-08-12 12:09 ` Yaakov (Cygwin/X)
2011-08-12 12:41 ` Yaakov (Cygwin/X)
2011-08-13 14:12 ` Corinna Vinschen [this message]
2011-08-14 19:30 ` Yaakov (Cygwin/X)
2011-08-15 4:03 ` Yaakov (Cygwin/X)
2011-08-15 7:42 ` Corinna Vinschen
2011-08-16 12:33 ` Dave Korn
2011-08-12 15:49 ` Dave Korn
2011-08-12 16:21 ` Yaakov (Cygwin/X)
2011-08-13 11:28 ` Corinna Vinschen
2011-08-13 16:20 ` Peter Rosin
2011-08-14 11:20 ` Corinna Vinschen
2011-08-14 23:01 ` Peter Rosin
2011-08-15 7:47 ` Corinna Vinschen
2011-10-16 21:19 ` Yaakov (Cygwin/X)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110813141124.GE4098@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).