public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Huber" <michael.huber@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc-4.1.1
Date: Wed, 7 Jun 2006 13:46:02 -0400	[thread overview]
Message-ID: <e1a7ee0c0606071046u129d6e75o92ce76308b5eb126@mail.gmail.com> (raw)
In-Reply-To: <4486F8F8.8090307@cisco.com>

I had some weird problems with the emerge -e system (libraries not
being properly identified to ./config scripts, that blocking issue
with pam.d & shadow, usual unstable tree stuff), but after toying with
it for a few hours, I have a successfully running desktop.

On 6/7/06, Roy Wright <royw@cisco.com> wrote:
> Mohammed Hagag wrote:
> > i just want to know if any one here have built a full desktop with
> > gcc-4.1.1 without problems ?
> > i have some problems with xf86 video drivers and some other ebuilds.
> >
> > i did a bootstartp from normal stage3 and i'm doing emerge -e world
> > now but some important packages did not compile most of the with
> > errors about glibc include files.
> >
> > any one here know any thing about these problems ??
> I did: emerge -s && emerge -e && revdep-rebuild
>
> You might want to read:
>
> http://forums.gentoo.org/viewtopic.php?t=282474&highlight=
>
> which basically recommends:
>
>   emerge -s
>   emerge -s
>   emerge -e
>   emerge -e
>
> to make sure the toolchain is built correctly.
>
> HTH,
> Roy
> --
> gentoo-user@gentoo.org mailing list
>
>
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-06-07 17:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ad4496950606070647s5a4bc702m8deeda7dbd590c4a@mail.gmail.com>
2006-06-07 13:53 ` [gentoo-user] gcc-4.1.1 Mohammed Hagag
2006-06-07 14:30   ` Peper
2006-06-07 14:35     ` Julien Cabillot
2006-06-07 14:45   ` Kristian Poul Herkild
2006-06-07 14:56   ` Neil Bothwick
2006-06-07 15:00   ` Bo Ørsted Andresen
2006-06-07 15:25   ` Conneries wearegeeks
2006-06-07 16:04   ` Roy Wright
2006-06-07 17:46     ` Mike Huber [this message]
2006-06-07 18:09       ` Daniel da Veiga
2006-06-07 19:27         ` Roy Wright
2006-06-07 19:55           ` Daniel da Veiga
2006-06-07 18:17       ` Evan Klitzke
2006-06-07 23:25     ` Richard Fish
2006-06-08  0:32       ` Evan Klitzke
2006-06-08  4:40         ` Richard Fish
2006-06-08 11:39           ` Mohammed Hagag
2006-06-08  1:50       ` Bob Young
2006-06-08  2:10         ` Jerry McBride
2006-06-12 21:35           ` Bob Young
2006-06-13  0:09             ` Richard Fish
2006-06-08  4:24         ` Richard Fish
2006-06-08 12:34           ` Bob Young
2006-06-08 13:31             ` Hans-Werner Hilse
2006-06-08 14:00               ` Bob Young
2006-06-08 14:28                 ` Bo Ørsted Andresen
2006-06-08 14:57                   ` Bob Young
2006-06-08 15:27                 ` Toby Cubitt
2006-06-08 18:05             ` Richard Fish
2006-06-09 11:50               ` Vladimir G. Ivanovic
2006-06-09 19:43                 ` Richard Fish
2006-06-16 17:25             ` Thomas T. Veldhouse
2006-06-16 17:50               ` Bob Young
2006-06-16 17:17         ` Thomas T. Veldhouse

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=e1a7ee0c0606071046u129d6e75o92ce76308b5eb126@mail.gmail.com \
    --to=michael.huber@gmail.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