public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo 2006.1 profile and use flag changes
Date: Sat, 02 Sep 2006 18:56:54 -0500	[thread overview]
Message-ID: <44FA1A46.1080908@vista-express.com> (raw)
In-Reply-To: <200609030048.32484.peter.ruskin@dsl.pipex.com>

Peter Ruskin wrote:
> On Saturday 02 September 2006 23:16, Dale wrote:
>   
>> The fact it doesn't exist is what I was curious about.  It looks
>> like they could create a list and/or thread on the forums to let
>> us know what is changing.  I want to get all the current "bugs"
>> worked out before I start changing profiles.  My emerge -e world
>> after the gcc upgrade is still in progress and some are not going
>> well.
>>     
>
> Same here ;-(
>
> This is the second time I've tried updating gcc to 4.1.1.  This time 
> emerge -e world failed on sys-fs/dazuko kde-base/kdewebdev 
> sys-apps/busybox app-office/openoffice kde-base/kdemultimedia and 
> sci-astronomy/celestia before I gave up and reverted to 3.4.4.
>
> I believe the time for gcc-4.1.1 is not yet right.
>
>   

Oh God.  Now we find this out.  O_O  Oh well.  I have BACK-UPS.  LOL

Dale

:-)  :-)
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-03  0:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02 14:04 [gentoo-user] Gentoo 2006.1 profile and use flag changes Daniel Pielmeier
2006-09-02 14:18 ` Bo Ørsted Andresen
2006-09-02 16:28   ` Dale
2006-09-02 21:05     ` b.n.
2006-09-02 19:32       ` Bo Ørsted Andresen
2006-09-02 21:33         ` Dale
2006-09-02 22:05           ` Bo Ørsted Andresen
2006-09-02 22:16             ` Dale
2006-09-02 23:48               ` Peter Ruskin
2006-09-02 23:56                 ` Dale [this message]
2006-09-03  2:37                 ` Richard Fish
2006-09-03 11:16                   ` Peter Ruskin
2006-09-03 12:33                   ` b.n.
2006-09-03 12:15                     ` Mick
2006-09-04  9:03                       ` Richard Fish
2006-09-04  9:16                     ` Richard Fish
2006-09-05  1:08                       ` b.n.
2006-09-04 23:45                         ` Richard Fish
2006-09-05 21:41                           ` b.n.
2006-09-06 22:35                             ` Richard Fish
2006-09-06 22:44                               ` Bo Ørsted Andresen
2006-09-06 23:24                                 ` Richard Fish
2006-09-06 22:46                               ` Donnie Berkholz
2006-09-06 23:48                                 ` Richard Fish
2006-09-07  0:24                                   ` Richard Fish
2006-09-07  0:26                                   ` Bo Ørsted Andresen
2006-09-07  0:41                                     ` Bo Ørsted Andresen
2006-09-07  0:42                                     ` Richard Fish
2006-09-07  1:11                                     ` Richard Fish
2006-09-03 14:07                   ` Peter Ruskin
2006-09-07 16:17                     ` Peter Ruskin
2006-09-04 17:38             ` Daniel Pielmeier
2006-09-02 23:18     ` Richard Fish
     [not found]       ` <44FA195C.2060403@vista-express.com>
2006-09-03  2:40         ` Richard Fish

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=44FA1A46.1080908@vista-express.com \
    --to=teendale@vista-express.com \
    --cc=gentoo-user@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