gcc build fails during emerge system on new 64-bit install
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?
#
# 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?
sys-devel/gcc-4.4.3-r2 was built with the following:
USE="fortran nptl (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -graphite -gtk (-hardened) (-libffi) -mudflap (-multilib) -multislot (-n32) (-n64) -nls -nocxx -objc -objc++ -objc-gc -openmp -test -vanilla"
CFLAGS="-O2 -march=native -pipe"
CXXFLAGS="-O2 -march=native -pipe"
06-24-2010, 06:28 AM
Stroller
gcc build fails during emerge system on new 64-bit install
On 24 Jun 2010, at 00:33, Walter Dnes wrote:
... 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.
Your motherboard doesn't need native PS2 ports: http://www.ledshoppe.com/Product/com/CA4036.htm
Stroller.
06-24-2010, 08:38 PM
Mick
gcc build fails during emerge system on new 64-bit install
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
06-25-2010, 02:56 AM
"Walter Dnes"
gcc build fails during emerge system on new 64-bit install
On Thu, Jun 24, 2010 at 07:28:14AM +0100, Stroller wrote
> On 24 Jun 2010, at 00:33, Walter Dnes wrote:
> > ... 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.
>
> Your motherboard doesn't need native PS2 ports: http://www.ledshoppe.com/Product/com/CA4036.htm
Hmmmm. Interesting. I assume that it's not your average passive
connector. Those don't work. "2. USB Bus Powered" probably means it
has keyboard emulation circuitry.
--
Walter Dnes <waltdnes@waltdnes.org>
06-25-2010, 03:29 AM
"Walter Dnes"
gcc build fails during emerge system on new 64-bit install
On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote
> 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.
If anything, I'll install a VM to run it in.
> Have you tried setting -j1 and trying emerging it once more?
I *ALWAYS* have -j1 in /etc/make.conf. Anyways, it turned out to be
something completely different. Whilst doing additional Google
searching, I stumbled across "Foolproof Gentoo World Update Build Order"
at http://foxpa.ws/tag/package-keywords/ and it was proof against this
fool, too <G>. My problem was that the Gentoo install snapshot put in
gcc-4.3.4, and "emerge --update world" pulled in gcc-4.4.3-r2. So far,
so good. But after the first build, I forgot to gcc-config over to
4.4.3-r2 ... dohhhhhhh.
Anyhow, after switching over, rebuilding gcc-4.4.3-r2, exiting,
logging back in, unmerging gcc-4.3.4, and rebuilding glibc, I
successfully emerged system and world. I'm now emerging xorg-x11.
<RANT>
Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a
kiosk machine at UN headquarters fer-cryin-out-loud.
</RANT>
--
Walter Dnes <waltdnes@waltdnes.org>
06-25-2010, 05:44 AM
Dale
gcc build fails during emerge system on new 64-bit install
Walter Dnes wrote:
On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote
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.
If anything, I'll install a VM to run it in.
Have you tried setting -j1 and trying emerging it once more?
I *ALWAYS* have -j1 in /etc/make.conf. Anyways, it turned out to be
something completely different. Whilst doing additional Google
searching, I stumbled across "Foolproof Gentoo World Update Build Order"
at http://foxpa.ws/tag/package-keywords/ and it was proof against this
fool, too<G>. My problem was that the Gentoo install snapshot put in
gcc-4.3.4, and "emerge --update world" pulled in gcc-4.4.3-r2. So far,
so good. But after the first build, I forgot to gcc-config over to
4.4.3-r2 ... dohhhhhhh.
Anyhow, after switching over, rebuilding gcc-4.4.3-r2, exiting,
logging back in, unmerging gcc-4.3.4, and rebuilding glibc, I
successfully emerged system and world. I'm now emerging xorg-x11.
<RANT>
Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a
kiosk machine at UN headquarters fer-cryin-out-loud.
</RANT>
For future reference, after you switch gcc, you should run env-update
and source /etc/profile. Then you don't have to log out and back in
again. One could argue that one is easier than the other tho. ;-)
Depends on the length of the password I guess.
Dale
:-) :-)
06-25-2010, 08:26 AM
Stroller
gcc build fails during emerge system on new 64-bit install
On 25 Jun 2010, at 03:56, Walter Dnes wrote:
On Thu, Jun 24, 2010 at 07:28:14AM +0100, Stroller wrote
On 24 Jun 2010, at 00:33, Walter Dnes wrote:
... 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.
Your motherboard doesn't need native PS2 ports: http://www.ledshoppe.com/Product/com/CA4036.htm
Hmmmm. Interesting. I assume that it's not your average passive
connector. Those don't work. "2. USB Bus Powered" probably means it
has keyboard emulation circuitry.
I assume it has some electronics in there. These are exceedingly
common, however, and make the keyboard appear to the o/s (and BIOS) as
a standard USB HCI device.
Stroller.
06-25-2010, 08:55 AM
Alex Schuster
gcc build fails during emerge system on new 64-bit install
Walter Dnes writes:
> On Thu, Jun 24, 2010 at 09:38:17PM +0100, Mick wrote
>
> > 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.
>
> If anything, I'll install a VM to run it in.
I'm curious. Are there advantages on not running a multilib profile?
> <RANT>
> Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
> cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a
> kiosk machine at UN headquarters fer-cryin-out-loud.
> </RANT>
xorg-x11 depends on them, I think there is no way to tell portage a
dependency is optional. Might be nice feature, though. Debian has
something like this I think, 'suggested packages' that may be installed
additionally if desired. Maybe an 'optional' use flag could do this? But
it would habe to be set for every package, not in the DEPEND list in the
xorg-x11 ebuild. A DEPEND_IF_NOT_MASKED entry in the ebuild would be nice.
Anyway, I do not install xorg-x11 at all, but xorg-server instead. Which
means I have to care about optional stuff for myself, like fonts, tools
like xdpyinfo and such. But at least I do not have cyrillic fonts on my
system
Wonko
06-25-2010, 10:53 AM
Neil Bothwick
gcc build fails during emerge system on new 64-bit install
On Thu, 24 Jun 2010 23:29:09 -0400, Walter Dnes wrote:
> <RANT>
> Why on earth will xorg-x11 *NOT* build if I mask out various arabic,
> cyrillic, ethiopic, and jis fonts? My PC is *NOT* intended to be a
> kiosk machine at UN headquarters fer-cryin-out-loud.
> </RANT>
Because xorg-x11 is metapackage that pulls everything in. If you want to
choose what is installed, either emerge components individually or
create a set.
--
Neil Bothwick
Copy from another: plagiarism. Copy from many: research.
06-26-2010, 08:31 PM
gcc build fails during emerge system on new 64-bit install
On Fri, Jun 25, 2010 at 12:44:47AM -0500, Dale wrote
> For future reference, after you switch gcc, you should run env-update
> and source /etc/profile. Then you don't have to log out and back in
> again. One could argue that one is easier than the other tho. ;-)
I knew I had to do a couple of things if I wanted to avoid logout and
login, but I couldn't remember off the top of my head. It was easier to
just log out+in rather than look it up.
gcc build fails during emerge system on new 64-bit install
