Bug 1895086 - ROOT reports "standard library mismatch", needs to be recompiled
Summary: ROOT reports "standard library mismatch", needs to be recompiled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: root
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Mattias Ellert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-05 17:23 UTC by Peifeng Liu
Modified: 2020-11-16 01:12 UTC (History)
1 user (show)

Fixed In Version: root-6.22.02-4.fc33 root-6.22.02-4.fc32
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-16 01:09:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peifeng Liu 2020-11-05 17:23:08 UTC
This is essentially same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1751407.

Description of problem:
ROOT complains of "standard library mismatch"

Version-Release number of selected component (if applicable):
6.22.02-3.fc33

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.22/02                        https://root.cern |
  | (c) 1995-2020, The ROOT Team; conception: R. Brun, F. Rademakers |
  | Built for linuxx8664gcc on Aug 17 2020, 12:46:52                 |
  | From tags/v6-22-02@v6-22-02                                      |
  | 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__ '20200826'
  Extraction of runtime standard library version was: '20201016'
hello


Expected results:
"hello" should be printed out without warning.

Additional info:

Comment 1 Fedora Update System 2020-11-07 20:01:55 UTC
FEDORA-2020-70eeb92795 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-70eeb92795

Comment 2 Fedora Update System 2020-11-07 20:01:55 UTC
FEDORA-2020-868b75ba7b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-868b75ba7b

Comment 3 Fedora Update System 2020-11-08 01:55:36 UTC
FEDORA-2020-868b75ba7b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-868b75ba7b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-868b75ba7b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2020-11-08 02:00:35 UTC
FEDORA-2020-70eeb92795 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-70eeb92795`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-70eeb92795

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Peifeng Liu 2020-11-09 17:06:12 UTC
I installed the update in Fedora 33 testing repository and the warning is gone. Thanks.

Comment 6 Fedora Update System 2020-11-16 01:09:00 UTC
FEDORA-2020-70eeb92795 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-11-16 01:12:43 UTC
FEDORA-2020-868b75ba7b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.