Bug 168662

Summary:	sys-devel/gcc-4.1.1-r3 fails parallel make during install of headers
Product:	Gentoo Linux	Reporter:	Thomas Koeller <thomas>
Component:	[OLD] Core system	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	gentoo
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Thomas Koeller 2007-02-28 00:03:14 UTC

Emerging gcc-4.1.1-r3 fails on a hyperthreading system if a parallel build "make -j3" is attempted. '/usr/gcc/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4' is created as a file, instead of being a directory. This kind of error is usually caused by incorrect make dependencies (File is copied to target directory which does not yet exist, resulting in a file with the name of the target directory).

Reproducible: Always

Steps to Reproduce:
On a system capable of parallel builds (hyperthreading or multi-core), emerge gcc with "MAKEFLAGS=-j3" in /etc/make.conf.

Actual Results:  
See description.

Expected Results:  
Emerge should finish cleanly.

Workaround is to do 'MAKEFLAGS=-j1 emerge gcc'.

Comment 1 SpanKY gentoo-dev

2007-03-04 20:54:34 UTC

ive seen this before (but not in Gentoo) ... i havent been able to narrow it down

Comment 2 Bruce Merry 2007-06-12 10:24:55 UTC

I have a related failure with 4.1.2: the g++-v4 directory is created, but the C++ headers are not placed inside. The emerge is successful, but any attempt to compile C++ code fails because the headers are missing. Fortunately C compilation still worked, so I was able to fix the problem.

The workaround is again to use -j1.

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2007-07-20 11:15:12 UTC

*** Bug 185971 has been marked as a duplicate of this bug. ***

Comment 4 Christian Schmidt 2007-07-20 11:34:30 UTC

Funnily, it works for me on:
- Dual Pentium 3 (-j3, x86)
- Athlon 64 X2 (-j3, ~amd64)
- Dual Dual-Core Opteron (-j5, amd64)
but fails on Core 2 Duo (-j3, ~amd64).

Comment 5 SpanKY gentoo-dev

2007-10-07 04:23:27 UTC


*** This bug has been marked as a duplicate of bug 177304 ***