Description of problem: Complaint of "Possible C++ standard library mismatch" when compiling a C++ file. Seems to be same as https://bugzilla.redhat.com/show_bug.cgi?id=1751407 and https://bugzilla.redhat.com/show_bug.cgi?id=1895086 Version-Release number of selected component (if applicable): root.x86_64 6.26.02-2.fc36 libstdc++.x86_64 12.1.1-1.fc36 How reproducible: Always Steps to Reproduce: 1.Write a C++ program #include <iostream> void hello() { std::cout<<"hello\n"; } 2. Let ROOT complile and run Actual results: $ root -b -q hello.C++ ------------------------------------------------------------------ | Welcome to ROOT 6.26/02 https://root.cern | | (c) 1995-2021, The ROOT Team; conception: R. Brun, F. Rademakers | | Built for linuxx8664gcc on Apr 12 2022, 16:28:03 | | From tags/v6-26-02@v6-26-02 | | With g++ (GCC) 12.0.1 20220413 (Red Hat 12.0.1-0) | | Try '.help', '.demo', '.license', '.credits', '.quit'/'.q' | ------------------------------------------------------------------ Processing hello.C++... Info in <TUnixSystem::ACLiC>: creating shared library /home/pliu/sandbox/./hello_C.so Warning in cling::IncrementalParser::CheckABICompatibility(): Possible C++ standard library mismatch, compiled with __GLIBCXX__ '20220413' Extraction of runtime standard library version was: '20220507' hello Expected results: "hello" should be printed out without warning. Additional info:
FEDORA-2022-0e2b41606a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0e2b41606a
FEDORA-2022-0e2b41606a has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0e2b41606a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0e2b41606a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0e2b41606a has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.