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
signature.asc
Description: This is a digitally signed message part.
