| Summary: | sys-devel/gcc-5.4.0-r1 fails compile tests for succeeding packages of emerge | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Derk W te Bokkel <derk.tebokkel> |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ab4bd, bkohler, brainsburn, gem, holger, josef64, marduk, oleg.hoefling, scottsshort, whissi |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=604084 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log for vlc
build.log for ffmpeg post gcc-5.4.0-r1 install config.log config.log from vlc work directory |
||
Created attachment 457460 [details]
build.log for ffmpeg post gcc-5.4.0-r1 install
another build fail due to compiler issues
selecting another compiler fixes the issue .. am rebuilding gcc-5.4.0 version now as it was fine .. this new snapshot is defective .. Can you attach config.log so we can see how/why the test fails? The -r1 release is a dumpster fire and needs to be undone/masked or fixed ASAP, since it results in a broken system gcc. Apparently it's a prerelease (?) of 5.4.1 with *some* parts already calling themselves 5.4.1 while others are still being installed under the old 5.4.0 path/names, creating a completely broken install that won't compile/link anything. I've been able to quickly fix things again by moving/renaming everything from any stale 5.4.0 directories to/into 5.4.1, manually renaming/editing the gcc-config entry in /etc/env.d/gcc and running gcc-config to get a working system again. it have been removed from the tree sorry for the broken gcc Created attachment 457462 [details]
config.log
config.log from where?? .. oh the build directory .. the one that failed does not exist .. but i stopped another build instance .. so ..
I was hoping to see this file as mentioned in the first build.log you attached: !!! Please attach the following file when seeking support: !!! /var/tmp/portage/media-video/vlc-2.2.4-r1/work/vlc-2.2.4/config.log Created attachment 457466 [details]
config.log from vlc work directory
here is the config.log you were expecting
do note that is the compiler that is the problem .. vlc and ffmpeg build fine when the compiler works :) I just used them as examples of the gcc fail to compile errors I find myself with a number of machines with not working c compiler. Some mainatainer had too much to drink on Christmas. I see gcc-5.4.0-r1 is now out of the tree, but can someone go into more detail on how to fix this cluster-fsck? Here is a partial recovery plan, I'll know in 30 mins if this is good enough: # su - # eix-sync # emerge -1a gcc # cd /etc/env.d/gcc # cp x86_64-pc-linux-gnu-5.4.0 x86_64-pc-linux-gnu-5.4.1 # vi config-x86_64-pc-linux-gnu x86_64-pc-linux-gnu-5.4.1 -- in vi change every 5.4.0 to 5.4.1 in the above 2 files -- # cp /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.0/libgcc_s.so /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.1/libgcc_s.so # cp /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.0/libstdc++.so /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.1/libstdc++.so (In reply to Holger Hoffstätte from comment #4) > The -r1 release is a dumpster fire and needs to be undone/masked or > fixed ASAP, since it results in a broken system gcc. > > Apparently it's a prerelease (?) of 5.4.1 with *some* parts already > calling themselves 5.4.1 while others are still being installed under > the old 5.4.0 path/names, creating a completely broken install that > won't compile/link anything. > > I've been able to quickly fix things again by moving/renaming everything > from any stale 5.4.0 directories to/into 5.4.1, manually renaming/editing > the gcc-config entry in /etc/env.d/gcc and running gcc-config to get a > working system again. Thanks for suggestion: I managed to get a working system following your advices. (In reply to Leonardo Ferraguzzi from comment #12) > (In reply to Holger Hoffstätte from comment #4) > > The -r1 release is a dumpster fire and needs to be undone/masked or > > fixed ASAP, since it results in a broken system gcc. > > > > Apparently it's a prerelease (?) of 5.4.1 with *some* parts already > > calling themselves 5.4.1 while others are still being installed under > > the old 5.4.0 path/names, creating a completely broken install that > > won't compile/link anything. > > > > I've been able to quickly fix things again by moving/renaming everything > > from any stale 5.4.0 directories to/into 5.4.1, manually renaming/editing > > the gcc-config entry in /etc/env.d/gcc and running gcc-config to get a > > working system again. > > Thanks for suggestion: I managed to get a working system following your > advices. does that mean same steps as in post 11 ? My steps in comment #11 seemed to work, but not extensively tested. All that was left after the emerge was to use gcc-config to reset the working gcc to version 4.5.0. I can compile again, but not sure if any lasting damage done. I'll wait a while before removing the broken gcc and burn that bridge. Removal may take some manual intervention. Something still not quite right. # eix mpm eix: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory The fix seemed to be: # cp /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.0/libstdc++.so.6 /usr/lib64/gcc/x86_64-pc-linux-gnu/5.4.1/libstdc++.so.6 Odd that the 5.4.1 directory is still being used... For fixing install a binary PORTAGE_BINHOST="http://packages.gentooexperimental.org/packages/amd64-unstable/" emerge -av1G =sys-devel/gcc-5.4.0 should work. thanks to Holger Hoffstätte Gary E. Miller (In reply to josef.95 from comment #16) > For fixing install a binary > PORTAGE_BINHOST="http://packages.gentooexperimental.org/packages/amd64- > unstable/" emerge -av1G =sys-devel/gcc-5.4.0 > should work. Yes indeed. Many thanks! First time I've done that... *** Bug 595642 has been marked as a duplicate of this bug. *** It's good to have 2 versions of GCC installed (5.* and 4.*). I just set gcc to 4.1.2 with gcc-config, masked gcc-5.4.0-r1 and installed gcc-5.4.0 which works fine. Fixed in gcc 5.4.0-r2 |
Created attachment 457458 [details] build.log for vlc last of the failing builds post gcc-5.4.0-r1 install