public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin-talk@cygwin.com
Subject: Re: GCC4, new package soon?
Date: Fri, 14 Aug 2009 20:26:00 -0000	[thread overview]
Message-ID: <4A85C871.7050106@cwilson.fastmail.fm> (raw)
In-Reply-To: <20090814200705.GA10492@ednor.casa.cgf.cx>

Christopher Faylor wrote:
> On Fri, Aug 14, 2009 at 04:01:46PM -0400, Charles Wilson wrote:
>> [snip]
>> There are a ton of things wrong with this behavior, but it is what it is
>> -- and somehow we need to work around it, until libtool is "fixed".
>> Whatever "fixed" means.
> 
>   find / -name 'libtool*' -o -name 'lt*' | xargs rm

Ouch. Harsh.

At the risk of having a technical discussion on the talk list, I wonder
what the ramifications would be of just not shipping .la files for the
gcc runtime libs?  It's possible that this would "trick" libtool into
just recording -lstdc++ etc, instead of canonicalizing to
/full/path/to/libstdc++.la.

Just a thought.

--
Chuck

  reply	other threads:[~2009-08-14 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090813083945.GH13438@calimero.vinschen.de>
     [not found] ` <4A842996.3050108@gmail.com>
     [not found]   ` <4A850F1E.2030707@users.sourceforge.net>
     [not found]     ` <4A8562EA.5010504@gmail.com>
     [not found]       ` <4A85A745.4050003@users.sourceforge.net>
     [not found]         ` <4A85B39D.3000502@gmail.com>
     [not found]           ` <4A85C2AA.1080105@cwilson.fastmail.fm>
2009-08-14 20:07             ` Christopher Faylor
2009-08-14 20:26               ` Charles Wilson [this message]
2009-08-14 20:29                 ` Dave Korn
2009-08-14 22:10                   ` Morgan Gangwere
2009-08-15  0:08                     ` Dave Korn
2009-08-15 12:40                       ` Morgan Gangwere

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=4A85C871.7050106@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin-talk@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).