From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Cc: JonY <10walls@gmail.com>
Subject: Re: Default manifest
Date: Wed, 21 May 2014 13:44:00 -0000 [thread overview]
Message-ID: <537CA7CC.7080709@cornell.edu> (raw)
In-Reply-To: <20140515075648.GL2436@calimero.vinschen.de>
On 5/15/2014 3:56 AM, Corinna Vinschen wrote:
> On May 15 01:25, Christopher Faylor wrote:
>> On Wed, May 14, 2014 at 08:07:26PM -0400, Ken Brown wrote:
>>> Are we close to a resolution of the problems with default manifests? It
>>> looks to me like all the pieces are in place, but maybe I've missed
>>> something:
>>>
>>> https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01387.html
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=16790#c9
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=16807#c8
>>>
>>> I'm not trying to rush any maintainers, but I'm asking because I
>>> currently have to use a self-built version of binutils, which doesn't
>>> provide a default manifest, because of the problem I reported here:
>>>
>>> http://cygwin.com/ml/cygwin/2014-04/msg00199.html
>>
>> I'll update binutils ASAP.
>
> For the default manifest to get going we also need the patcha new GCC
> with Nick's patch from
>
> https://gcc.gnu.org/ml/gcc-patches/2014-04/msg01378.html
>
> Is that easily backportable to GCC 4.8, or does 4.8 not support the
> %if-exists functionality?
JonY, any chance we could get a release of GCC that includes this patch?
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-21 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 1:56 Ken Brown
2014-05-15 7:17 ` Christopher Faylor
2014-05-15 12:41 ` Corinna Vinschen
2014-05-21 13:44 ` Ken Brown [this message]
2014-05-21 15:53 ` JonY
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=537CA7CC.7080709@cornell.edu \
--to=kbrown@cornell.edu \
--cc=10walls@gmail.com \
--cc=cygwin@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).