Bug 1472424

Summary: emacs: relocation error: /lib64/libjavascriptcoregtk-4.0.so.18: symbol _ZSt11__once_call, version GLIBCXX_3.4.11 not defined in file libstdc++.so.6 with link time reference
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: davejohansen, fweimer, jakub, jonathan.underwood, jsynacek, jwakely, law, mpolacek, msekleta, phracek
Target Milestone: ---   
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-18 21:06:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard W.M. Jones 2017-07-18 17:00:51 UTC 
Description of problem:

This happens on POWER8 (ppc64le) only.

When you run emacs it doesn't start up.  Instead it crashes with:

emacs: relocation error: /lib64/libjavascriptcoregtk-4.0.so.18: symbol _ZSt11__once_call, version GLIBCXX_3.4.11 not defined in file libstdc++.so.6 with link time reference

Actually this might be a problem in webkit or even libstdc++.

Version-Release number of selected component (if applicable):

emacs-1:25.2-2.fc27.ppc64le
webkitgtk4-2.16.2-2.fc27.ppc64le

How reproducible:

Happened once.

Steps to Reproduce:
1. Run emacs.
Comment 1 Richard W.M. Jones 2017-07-18 17:14:30 UTC 
Weirdly this doesn't happen on ppc64 (big endian).
Comment 2 Richard W.M. Jones 2017-07-18 20:09:19 UTC 
libstdc++-7.1.1-3.fc26.ppc64le => good

libstdc++-7.1.1-5.fc27.ppc64le => bad

This happens with both webkitgtk4-2.16.5-1.fc26 & webkitgtk4-2.16.2-2.fc27
(why is F26 newer than Rawhide)?

Possibly the problem is that webkitgtk4 needs rebuilding against
newer libstdc++ however.  I'll take a look into the code next.
Comment 3 Florian Weimer 2017-07-18 21:06:57 UTC 

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