Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 642376 - sys-devel/gcc-6.4.0 doesn't compile under profile 17.1 on amd64
Summary: sys-devel/gcc-6.4.0 doesn't compile under profile 17.1 on amd64
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Eclasses (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-27 07:11 UTC by Maurice Volaski
Modified: 2018-01-09 05:37 UTC (History)
2 users (show)

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


Attachments
emerge info (file_642376.txt,5.30 KB, text/plain)
2017-12-27 07:11 UTC, Maurice Volaski
Details
build log (gcc-build-logs.tar.bz2,105.58 KB, application/x-bzip2)
2017-12-27 15:50 UTC, Maurice Volaski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maurice Volaski 2017-12-27 07:11:32 UTC
Created attachment 511712 [details]
emerge info

The error is 
/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 
collect2: error: ld returned 1 exit status 
make[5]: *** [Makefile:950: libgcc_s.so] Error 1 
make[5]: Leaving directory '/var/tmp/portage/sys-devel/gcc-6.4.0/work/build/x86_64-pc-linux-gnu/32/libgcc' 
make[4]: *** [Makefile:1161: multi-do] Error 1 
make[4]: Leaving directory '/var/tmp/portage/sys-devel/gcc-6.4.0/work/build/x86_64-pc-linux-gnu/libgcc' 
make[3]: *** [Makefile:120: all-multi] Error 2 
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-6.4.0/work/build/x86_64-pc-linux-gnu/libgcc' 
make[2]: *** [Makefile:15659: all-stage1-target-libgcc] Error 2 
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-6.4.0/work/build' 
make[1]: *** [Makefile:20222: stage1-bubble] Error 2 
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-6.4.0/work/build' 
make: *** [Makefile:20554: bootstrap-lean] Error 2
Comment 1 Tomáš Mózes 2017-12-27 07:40:34 UTC
Please always attach the full build log.
Comment 2 Jonas Stein gentoo-dev 2017-12-27 11:27:12 UTC
Please *attach* the logfiles,
https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket
and reopen this ticket (Status:unconfirmed).
Comment 3 Maurice Volaski 2017-12-27 15:50:51 UTC
Created attachment 511760 [details]
build log
Comment 4 Maurice Volaski 2017-12-27 15:51:27 UTC
By the way, it compiles under profile 17.0.
Comment 5 Alexander Tsoy 2017-12-27 21:51:58 UTC
Have you performed the migration as explained in the news item?
Comment 6 Maurice Volaski 2018-01-08 19:51:27 UTC
I didn't perform the migration as described. That's because I wasn't even aware the 17.1 profile was experimental. I do believe there is a bug that can be addressed here. Experimental profiles showing up in eselect profile list should be marked this way. And then when selecting them, there should be output to point out that there are prerequisites to selecting such a profile. In other words, it's not simply enough to warn users in Gentoo News.

It appears that the 17.1 profile was removed, at least on a new install I am not seeing it any longer in the profile list.
Comment 7 Alexander Tsoy 2018-01-09 05:37:53 UTC
(In reply to Maurice Volaski from comment #6)
> I didn't perform the migration as described. That's because I wasn't even
> aware the 17.1 profile was experimental. I do believe there is a bug that
> can be addressed here. Experimental profiles showing up in eselect profile
> list should be marked this way. And then when selecting them, there should
> be output to point out that there are prerequisites to selecting such a
> profile. In other words, it's not simply enough to warn users in Gentoo News.

See bug 643864