Bug 964589 - /usr/bin/gcc-ar fails: "Cannot find binary 'ar'"
/usr/bin/gcc-ar fails: "Cannot find binary 'ar'"
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
Depends On:
Blocks: 974853
  Show dependency treegraph
Reported: 2013-05-19 00:54 EDT by Jay Finger
Modified: 2015-02-17 10:16 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 974853 (view as bug list)
Last Closed: 2015-02-17 10:16:08 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Finger 2013-05-19 00:54:31 EDT
Description of problem:

The "gcc-ar" program worked fine in F18.  In F19 Beta RC2 it always fails with "Cannot find binary 'ar'"  "gcc-ar" is necessary for anybody who wants to use the "-lto" feature with gcc.  

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

 $ yum whatprovides `which gcc-ar`
gcc-4.8.0-2.fc19.x86_64 : Various compilers (C, C++, Objective-C, Java, ...)
Repo        : @fedora
Matched from:
Filename    : /usr/bin/gcc-ar

How reproducible:

Steps to Reproduce:
1. Invoke gcc-ar on any .a file you have.  For example:  gcc-ar t /usr/lib64/libg.a
2. Observe error message
Actual results:

$ gcc-ar t /usr/lib64/libg.a
gcc-ar: Cannot find binary 'ar'

Expected results:

$ gcc-ar t /usr/lib64/libg.a

Additional info:

Anybody whose project requires gcc's link time optimization is going to be broken by this.  It means I cannot use stock F19 as a development platform.
Comment 1 Jay Finger 2013-05-19 12:06:31 EDT
From looking at strace output, gcc-ar is looking in the following two places for ar:

3569  stat("/usr/lib/gcc/x86_64-redhat-linux/4.8.0/../../../../x86_64-redhat-linux/bin/ar", 0x7fffa0b1fa00) = -1 ENOENT (No such file or directory)
3569  stat("/usr/libexec/gcc/x86_64-redhat-linux/4.8.0/ar", 0x7fffa0b1fa00) = -1 ENOENT (No such file or directory)
3569  write(2, "gcc-ar: Cannot find binary 'ar'\n", 32) = 32
3569  exit_group(1)                     = ?
3569  +++ exited with 1 +++

From going through changelogs, apparently the tools expect ar (and nm and ranlib) to be installed at /usr/libexec/gcc/x86_64-redhat-linux/4.8.0.  Or I guess to be hardlinked to those places, since we obviously still want those tools at /usr/bin as well.
Comment 2 Fedora End Of Life 2015-01-09 13:08:58 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2015-02-17 10:16:08 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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