public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Can not compile gcc
Date: Sat, 15 Nov 2008 06:41:43 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.11.15.06.41.43@cox.net> (raw)
In-Reply-To: 2a21586d0811141858h285d1e98ka29524bc2d74ed47@mail.gmail.com

"Mansour Al Akeel" <mansour.alakeel@gmail.com> posted
2a21586d0811141858h285d1e98ka29524bc2d74ed47@mail.gmail.com, excerpted
below, on  Fri, 14 Nov 2008 22:58:41 -0400:

> After I enabled IA32_EMULATION everything went fine. gcc emerge was
> succefull and installed glibc, now I am installing gnome. 

Cool! =:^)

> Since I am new
> to gentoo, I decided to have a look at the profile concept. In the
> future, if I find that I don't need the 32-bit java plugin for applets
> or flash or drivers for my wireless, nvidia ... etc, I will reconsider
> switching my profile to no-multilib. I am expecting a lot of issues to
> resolve when I do so, but that's ok.

Profiles are a neat concept, indeed.  It's very useful to be able to set 
a desktop or server, or no-multilb, profile, and have it "magically" set 
many USE flags and some other stuff appropriately, without having to set 
each one individually.

If you stick around for awhile, new profiles come online with support for 
new features, and old ones may be deprecated.  There's a nice howto guide 
for changing or upgrading your profile, when the time comes, but it's 
generally quite easy, and because Gentoo normally does rolling upgrades, 
making individual package upgrades available as they come out, you've 
usually upgraded nearly all your packages before changing the profile, 
and it's MUCH MUCH easier than upgrading from one release to another of a 
binary distribution.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2008-11-15  6:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 18:02 [gentoo-amd64] Can not compile gcc Mansour Al Akeel
2008-11-14 18:26 ` Barry Schwartz
2008-11-14 18:34   ` Justin
2008-11-14 19:31     ` Branko Badrljica
2008-11-14 18:40       ` Justin
2008-11-14 19:14         ` Mansour Al Akeel
2008-11-14 19:24           ` Beso
2008-11-14 19:30 ` [gentoo-amd64] " Duncan
2008-11-14 19:54   ` Mansour Al Akeel
2008-11-14 21:16     ` [gentoo-amd64] " Tonko Mulder
2008-11-14 21:23       ` Mansour Al Akeel
2008-11-14 23:44     ` [gentoo-amd64] " Duncan
2008-11-15  2:58       ` Mansour Al Akeel
2008-11-15  6:41         ` Duncan [this message]
2008-11-14 21:48 ` [gentoo-amd64] " Christoph Mende
2008-11-14 22:22   ` Mansour Al Akeel
2008-11-14 23:19     ` Branko Badrljica
2008-11-14 22:31       ` Beso
2008-11-14 23:10         ` Mansour Al Akeel
2008-11-14 23:26           ` Beso

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=pan.2008.11.15.06.41.43@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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