Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1623078 - libtool is missing gcc and gcc-c++ build requires
Summary: libtool is missing gcc and gcc-c++ build requires
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libtool
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-28 12:45 UTC by Marek Kašík
Modified: 2018-09-21 05:22 UTC (History)
7 users (show)

Fixed In Version: libtool-2.4.6-27.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-28 13:24:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Marek Kašík 2018-08-28 12:45:16 UTC 
Description of problem:
libtool is missing gcc and gcc-c++ build requires and a lot of variables inside "/usr/bin/libtool" is not defined because of that. Evince does not build consequently.
Look at diff of /usr/bin/libtool from Fedora 28 and Fedora 29.


Version-Release number of selected component (if applicable):
libtool-2.4.6-26.fc29 (and also rawhide)
Comment 1 Pavel Raiskup 2018-08-28 13:20:02 UTC 
Good point, thanks for the report!
Comment 2 Pavel Raiskup 2018-08-28 13:24:54 UTC 
https://src.fedoraproject.org/rpms/libtool/c/d7abc1ef1ac4ba4e6725ad0dde04070c559ca016?branch=master
Comment 3 Igor Raits 2018-08-28 16:37:51 UTC 
(In reply to Pavel Raiskup from comment #2)
> https://src.fedoraproject.org/rpms/libtool/c/
> d7abc1ef1ac4ba4e6725ad0dde04070c559ca016?branch=master

does it mean that whatever uses libtool has to be in c++?

IMO this change is entirely wrong because it's packages which should put BR not only for libtool but also for compilers.

I'm pretty sure libtool can function without compilers.
Comment 4 Pavel Raiskup 2018-08-28 21:32:10 UTC 
(In reply to Igor Gnatenko from comment #3)
> does it mean that whatever uses libtool has to be in c++?

It means that the /bin/libtool is capable to build c++ projects.  Ideally,
that /bin/libtool script wouldn't be used for package builds, but well... 

> IMO this change is entirely wrong because it's packages which should put BR
> not only for libtool but also for compilers.

I don't understand this, can you elaborate?

> I'm pretty sure libtool can function without compilers.

Yup, but diff the /bin/libtool with/without g++ in BR.
Comment 5 Igor Raits 2018-08-28 21:39:13 UTC 
I'm completely blind, I thought it is Requires.

Ignore everything what I said.
Comment 6 Marek Kašík 2018-08-29 09:11:00 UTC 
Hi,

could you create an update for this for Fedora 29? We are required to do updates via bodhi since yesterday. Thanks.
Comment 7 Fedora Update System 2018-08-29 10:03:51 UTC 
libtool-2.4.6-27.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8500fd9cad
Comment 8 Pavel Raiskup 2018-08-29 10:04:15 UTC 
Done, thanks for the ping.
Comment 9 Fedora Update System 2018-08-29 19:07:17 UTC 
libtool-2.4.6-27.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8500fd9cad
Comment 10 Fedora Update System 2018-08-29 23:14:13 UTC 
libtool-2.4.6-27.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8500fd9cad
Comment 11 Fedora Update System 2018-09-21 05:22:38 UTC 
libtool-2.4.6-27.fc29 has been pushed to the Fedora 29 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.