public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gcc-3.3.5.20050110-r1 for stable
Date: Sun, 10 Apr 2005 23:22:10 +0200	[thread overview]
Message-ID: <1113168130.4128.1.camel@Darkmere> (raw)
In-Reply-To: <200504101622.01557.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 618 bytes --]

On Sun, 2005-04-10 at 16:22 -0400, Mike Frysinger wrote:
> On Sunday 10 April 2005 11:31 am, Spider wrote:
> >  A touch late, but this uncovered a bug in libtool.
> 
> re-emerge libtool and it'll fix itself


Yep, I know that. 

Unfortunately, thats -not- going to be a "solution" for the people who
just installed 2005.0, got a gcc update and suddenly everything broke.

the ~x86 version doesn't exhibit this problem, btw.  stabilizing this
version might be prudent.

//Spider

-- 
begin  .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-10 21:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-08  3:46 [gentoo-dev] gcc-3.3.5.20050110-r1 for stable Mike Frysinger
2005-04-08 11:19 ` Dan Meltzer
2005-04-08 11:56   ` Stefan Sperling
2005-04-08 11:35 ` Ferris McCormick
2005-04-08 12:09   ` Stefan Sperling
2005-04-09  6:24   ` [gentoo-dev] List-Unsubscribe ren tie'nan
2005-04-08 12:00 ` [gentoo-dev] gcc-3.3.5.20050110-r1 for stable Stefan Sperling
2005-04-08 13:15 ` Mike Frysinger
2005-04-10 15:31 ` Spider
2005-04-10 20:22   ` Mike Frysinger
2005-04-10 21:22     ` Spider [this message]
2005-04-10 22:16       ` M. Edward (Ed) Borasky
2005-04-10 23:33       ` Mike Frysinger
2005-04-11 11:24         ` Francesco Riosa
2005-04-11 11:38           ` Francesco Riosa
2005-04-11 12:46           ` Mike Frysinger
2005-04-11 13:22             ` Francesco Riosa
2005-04-11 14:06               ` Stefan Sperling

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=1113168130.4128.1.camel@Darkmere \
    --to=spider@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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