Bug 959206 - gcc-c++ should be set as Requires
Summary: gcc-c++ should be set as Requires
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abi-compliance-checker
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-03 10:50 UTC by Dan Horák
Modified: 2013-06-29 18:31 UTC (History)
3 users (show)

Fixed In Version: abi-compliance-checker-1.99-1.fc19
Clone Of:
Environment:
Last Closed: 2013-06-23 05:55:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dan Horák 2013-05-03 10:50:14 UTC
on system without gcc-c++ package installed one gets:

[root@devel1 libica]# abi-compliance-checker -l libica -dump libica-22.xml 
Using GCC 4.7.2 (s390x-redhat-linux)
checking header(s) 2.2 ...
ERROR: some errors occurred when compiling headers
ERROR: see log for details:
  /root/libica/logs/libica/2.2/log.txt

ERROR: can't compile header(s)
Did you install G++?


Version-Release number of selected component (if applicable):
abi-compliance-checker-1.98.8-1.fc18


Solution:
add Requires: gcc-c++

Comment 1 Richard Shaw 2013-05-26 13:12:10 UTC
I added this but forgot to put this bug number in the bodhi update. Closing.

Comment 2 Dan Horák 2013-05-26 13:22:10 UTC
Richard, I can't find updates for abi-compliance-checker-1.98.8-2 in bodhi at all.

Comment 3 Richard Shaw 2013-05-26 13:53:41 UTC
Whoops. I knew I did the build, I guess that's the part I forgot :)...

Comment 4 Fedora Update System 2013-05-26 13:56:01 UTC
abi-compliance-checker-1.98.8-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/abi-compliance-checker-1.98.8-2.fc19

Comment 5 Fedora Update System 2013-05-26 13:56:10 UTC
abi-compliance-checker-1.98.8-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/abi-compliance-checker-1.98.8-2.fc18

Comment 6 Fedora Update System 2013-05-26 13:56:19 UTC
abi-compliance-checker-1.98.8-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abi-compliance-checker-1.98.8-2.fc17

Comment 7 Fedora Update System 2013-05-26 17:01:37 UTC
Package abi-compliance-checker-1.98.8-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abi-compliance-checker-1.98.8-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9309/abi-compliance-checker-1.98.8-2.fc19
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-05-29 12:48:43 UTC
abi-compliance-checker-1.99-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/abi-compliance-checker-1.99-1.fc18

Comment 9 Fedora Update System 2013-05-29 12:48:58 UTC
abi-compliance-checker-1.99-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/abi-compliance-checker-1.99-1.fc17

Comment 10 Fedora Update System 2013-05-29 12:49:16 UTC
abi-compliance-checker-1.99-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/abi-compliance-checker-1.99-1.fc19

Comment 11 Fedora Update System 2013-06-23 05:55:09 UTC
abi-compliance-checker-1.99-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2013-06-23 05:59:32 UTC
abi-compliance-checker-1.99-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2013-06-29 18:31:17 UTC
abi-compliance-checker-1.99-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, 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.