public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mansour Al Akeel" <mansour.alakeel@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Can not compile gcc
Date: Fri, 14 Nov 2008 19:10:04 -0400	[thread overview]
Message-ID: <2a21586d0811141510p5aaae310k7da3f8cf3cb0af79@mail.gmail.com> (raw)
In-Reply-To: <d257c3560811141431q3653f694n96ed2c148e441640@mail.gmail.com>

I am not gentoo expert and no idea about profiles. However that's what I got:

lrwxrwxrwx 1 root root    50 Nov 13 17:22 make.profile ->
../usr/portage/profiles/default/linux/amd64/2008.0
-rw-r--r-- 1 root root  2141 Jun 16 22:51 profile
-rw-r--r-- 1 root root   815 Nov 14 16:12 profile.env

I am emerging gcc again. I will see how things will go. In the mean
while I am looking into disabling multilib and remove it. I just don't
know how, and googling a bit while the emerge process is running.



On Fri, Nov 14, 2008 at 6:31 PM, Beso <givemesugarr@gmail.com> wrote:
> 2008/11/14 Branko Badrljica <brankob@avtomatika.com>:
>> Mansour Al Akeel wrote:
>>>
>>> Just out of curiosity, how did you know that IA32_EMULATION is not
>>> enabled? Which message told you this ?
>>>
>>>
>>
>> He probably just suspected. Kernel's inability to run 32-bit code could be
>> one of the reasons why the test code run failed.
>> Other reason might be some linking error or somesuch...
>
>
> the ability to compile other stuff tells that you're having problems
> with the multilib profile. i suspect that you're working on a
> no-multilib profile, instead.
> try a ls -l /etc | grep profile and see where the actual profile is poiting.
>
> --
> dott. ing. beso
>
>



  reply	other threads:[~2008-11-14 23:10 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
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 [this message]
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=2a21586d0811141510p5aaae310k7da3f8cf3cb0af79@mail.gmail.com \
    --to=mansour.alakeel@gmail.com \
    --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