public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc build fails during emerge system on new 64-bit install
Date: Thu, 24 Jun 2010 21:38:17 +0100	[thread overview]
Message-ID: <201006242138.18010.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20100623233324.GA11305@waltdnes.org>

[-- Attachment #1: Type: Text/Plain, Size: 1672 bytes --]

On Thursday 24 June 2010 00:33:24 Walter Dnes wrote:
>   This is my first attempt at 64-bit mode.  I have a shiny new Intel i3
> with 8 gigs ram on an MSI motherboard.  I got it custom-built locally in
> north Toronto, rather than ordering from Dell.  The MSI motherboard has
> PS/2 ports (YES!!!) so I don't have to tearfully throw away my genuine
> IBM PS/2 "clickety-clack" keyboard.  I selected the profile...
> 
> default/linux/amd64/10.0/no-multilib
> 
> ...to go whole-hog 64-bit.  Does leaving IA32_EMULATION on cause a
> problem?

I thought that you can't have IA32_emulation without multilib ... 

Is there a reason why you don't go for a usual desktop profile with multilib?  
I'll repeat the advice I was given in this list sometime around last Christmas 
(but can't find the thread now): you're bound to find some pesky application 
which is only available in 32bit and then you'll curse for having to 
reinstall.

> #
> # Executable file formats / Emulations
> #
> CONFIG_BINFMT_ELF=y
> CONFIG_COMPAT_BINFMT_ELF=y
> CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
> # CONFIG_HAVE_AOUT is not set
> CONFIG_BINFMT_MISC=y
> CONFIG_IA32_EMULATION=y
> # CONFIG_IA32_AOUT is not set
> CONFIG_COMPAT=y
> CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
> CONFIG_SYSVIPC_COMPAT=y
> CONFIG_NET=y
> CONFIG_COMPAT_NETLINK_MESSAGES=y
> 
>   I've attached the tail-end of the build log file of gcc-4.4.3-r2, as
> well as output from "emerge --info" and "emerge -pqv".  I have a quite
> conservative make.conf.  Any ideas about the problem, or even better, a
> solution?

Have you tried setting -j1 and trying emerging it once more?
-- 
Regards,
Mick

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

  parent reply	other threads:[~2010-06-24 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 23:33 [gentoo-user] gcc build fails during emerge system on new 64-bit install Walter Dnes
2010-06-24  6:28 ` Stroller
2010-06-25  2:56   ` Walter Dnes
2010-06-25  8:26     ` Stroller
2010-06-27 10:01       ` Peter Humphrey
2010-06-24 20:38 ` Mick [this message]
2010-06-25  3:29   ` [gentoo-user] [SOLVED] " Walter Dnes
2010-06-25  5:44     ` Dale
2010-06-26 20:31       ` waltdnes
2010-06-25  8:55     ` Alex Schuster
2010-06-25 10:53     ` Neil Bothwick

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=201006242138.18010.michaelkintzios@gmail.com \
    --to=michaelkintzios@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