Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 664338 - sys-devel/gcc-8.2 Link tests called after GCC_NO_EXECUTABLES resulting in stage 1 build failure
Summary: sys-devel/gcc-8.2 Link tests called after GCC_NO_EXECUTABLES resulting in sta...
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-23 01:43 UTC by ephemer0l
Modified: 2019-01-27 11:41 UTC (History)
3 users (show)

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

Attachments
build log (build.log.tar.bz2,55.25 KB, application/x-bzip)
2018-08-23 01:46 UTC, ephemer0l 		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 ephemer0l 2018-08-23 01:43:58 UTC 
<snip>
checking if /var/tmp/portage/sys-devel/gcc-8.2.0-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-8.2.0-r2/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-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include    supports -c -o file.o... (cached) yes
checking whether the /var/tmp/portage/sys-devel/gcc-8.2.0-r2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-8.2.0-r2/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-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include    linker (/var/tmp/portage/sys-devel/gcc-8.2.0-r2/work/build/./gcc/collect-ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
make[2]: *** [Makefile:14618: configure-stage1-target-libstdc++-v3] Error 1
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-8.2.0-r2/work/build'
make[1]: *** [Makefile:22082: stage1-bubble] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-8.2.0-r2/work/build'
make: *** [Makefile:22973: profiledbootstrap] Error 2
</snip>

Build log atached.
Comment 1 ephemer0l 2018-08-23 01:46:07 UTC 
Created attachment 544598 [details]
build log
Comment 2 Greg Turner 2018-08-23 03:04:28 UTC 
This "smells" parallel-build related.  What happens if you turn right around after this error and invoke:

  ebuild $(portageq envvar PORTDIR)/sys-devel/gcc/gcc-8.2.0-r2.ebuild compile

?

To be clear, not dismissing your problem, as a parallel-build issue is still an issue, as obviously toolchain ebuilds ought to be (and usually are) as robust as possible in the face of MAKEOPTS="-j$((RANDOM/128))".
Comment 3 Sergei Trofimovich (RETIRED) gentoo-dev 2018-08-27 08:55:41 UTC 
1. Can you also attach 'emerge --info gcc' if that system?

2. Also, gcc ebuild package all relevant build logs and asks to attach those as well. Can you do that? Namely it says:

   """* Please include /var/tmp/portage/sys-devel/gcc-8.2.0-r2/work/gcc-build-logs.tar.bz2 in your bug report."""

3. Is build failure reproducible?
Comment 4 Sergei Trofimovich (RETIRED) gentoo-dev 2019-01-27 11:41:33 UTC 
Closing after a timeout. Feel free to file a new bug with some details if it happens again. gcc-build-logs.tar.bz2 would be most useful.