public inbox for
 help / color / mirror / Atom feed
From: Christopher Faylor <>
Subject: Re: rebaseall [1.7]: cyggcc_s-1.dll error
Date: Tue, 29 Jun 2010 15:29:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Jun 29, 2010 at 04:51:37PM +0200, Corinna Vinschen wrote:
>On Jun 29 10:40, Christopher Faylor wrote:
>> On Tue, Jun 29, 2010 at 08:35:53AM -0600, Eric Blake wrote:
>> >On 06/29/2010 08:34 AM, Charles Wilson wrote:
>> >> Eric Blake wrote:
>> >>> Phooey.  dash now depends on cyggcc_s-1.dll, so rebaseall needs to be
>> >>> taught to add this library to the list of exemptions (similar to
>> >>> cygwin1.dll).
>> >> 
>> >> Or dash could be rebuilt using -static-libgcc.  It's not like dash needs
>> >> to worry about throwing C++ exceptions across DLL boundaries, and if
>> >> dash is meant to be a /bin/sh implementation (even if cygwin still uses
>> >> bash for that), then IMO it ought to be -- insofar as is possible --
>> >> statically linked.
>> >
>> >OK, I'm now trying to figure out how to add -static-libgcc into my
>> >cygport file.  Look for an updated dash later today...
>> In the meantime, you might want to consider linking dash with -static-libgcc.
>There's a good chance that Eric will have bad dreams about hundreds
>of tiny static libgcc's biting and clawing there way into his house
>tonight, and all he has for defense is a single gcc4 knife...

I picture little libgcc's carrying balloons which they rapidly rub on
their bodies, holding out their fingers to zap the unwary...


  reply	other threads:[~2010-06-29 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
2010-06-29 14:51     ` Corinna Vinschen
2010-06-29 15:29       ` Christopher Faylor [this message]
2010-06-29 15:40         ` Corinna Vinschen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).