642684 – GCC 6.4.0 Failed To Emerge

Bug 642684 - GCC 6.4.0 Failed To Emerge

Summary: GCC 6.4.0 Failed To Emerge

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2017-12-29 22:49 UTC by Alex Nagy
Modified:	2018-01-03 03:04 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge --info gcc 6.4.0 (emerge-info.gcc.log,5.89 KB, text/x-log) 2017-12-29 22:49 UTC, Alex Nagy	Details
gcc-6.4.0 build log with 17.1 profile (gcc-6.4.0_build.tar.xz,49.09 KB, application/x-xz) 2018-01-02 13:44 UTC, Daniel Schury	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alex Nagy 2017-12-29 22:49:15 UTC

Created attachment 512008 [details]
emerge --info gcc 6.4.0

New installation following handbook, makeopts set to -j5 (quad core Xeon W3550). 

output of emerge -pqv '=sys-devel/gcc-6.4.0' 
[ebuild   R   ] sys-devel/gcc-6.4.0  USE="cxx fortran (multilib) nls nptl openmp pch (pie*) sanitize ssp vtv (-altivec) (-awt) -cilk -debug -doc (-fixed-point) (-gcj) -go -graphite (-hardened) (-jit) (-libssp) -mpx -objc -objc++ -objc-gc -pgo -regression-test -vanilla" 

 * IMPORTANT: 10 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

Profile 33 selected (amd64/desktop/plasma)

Comment 1 Alex Nagy 2017-12-30 02:12:32 UTC

I was using 17.1 release, but backed off to 17.0 and everything seems to be working. Hohpe y'all can fix this.

Comment 2 Martin Väth 2017-12-30 05:08:15 UTC

Please attach the logfile. Without this, it is impossible to guess what went wrong in your case.

Comment 3 Daniel Schury 2018-01-02 13:44:20 UTC

Created attachment 512716 [details]
gcc-6.4.0 build log with 17.1 profile

Comment 4 Daniel Schury 2018-01-02 13:46:30 UTC

I guess I ran into the same problem as mentioned here[0] so I attached my build log. The last lines contain the problem:
»# @multilib_flags@ is still needed because this may use
# /var/tmp/portage/sys-devel/gcc-6.4.0/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-6.4.0/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linu$
# @multilib_dir@ is not really necessary, but sometimes it has
# more uses than just a directory name.
/bin/bash /var/tmp/portage/sys-devel/gcc-6.4.0/work/gcc-6.4.0/libgcc/../mkinstalldirs 32
mkdir -p -- 32
/var/tmp/portage/sys-devel/gcc-6.4.0/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-6.4.0/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-$
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/../lib/libc.so when searching for -lc
/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/../lib/libc.a when searching for -lc
/usr/x86_64-pc-linux-gnu/bin/ld: i386:x86-64 architecture of input file `/usr/lib/../lib/crti.o' is incompatible with i386 output
/usr/x86_64-pc-linux-gnu/bin/ld: i386:x86-64 architecture of input file `/usr/lib/../lib/crtn.o' is incompatible with i386 output
«

[0]