Bug 947899 - Cannot build 32-bit packages on Fedora 19 host
Summary: Cannot build 32-bit packages on Fedora 19 host
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Clark Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-03 13:54 UTC by Michael Cronenworth
Modified: 2015-06-29 11:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 11:51:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
log files (30.00 KB, application/x-xz)
2013-04-03 13:54 UTC, Michael Cronenworth
no flags Details

Description Michael Cronenworth 2013-04-03 13:54:13 UTC
Created attachment 731188 [details]
log files

Description of problem:
I had to build my first RHEL5 and F18 packages today after upgrading my
Koji server from Fedora 17 to 18. I cannot build 32-bit RHEL5 or F18 packages,
but RHEL6 packages compile fine. All packages built successfully under
Fedora 17.


Version-Release number of selected component (if applicable):
mock-1.1.30-1.fc18.noarch


How reproducible:
32-bit packages always fail to build for RHEL5 and F18 targets.


Steps to Reproduce:
Build any C package to a RHEL5 or F18 target on a F18 host with a 3.8+ kernel.

  
Actual results:
Build fails. GCC is unable to compile.
F18 packages: collect2: fatal error: cannot find 'ld'
RHEL5 packages: gcc: error trying to exec 'cc1': execvp: No such file or directory


Expected results:
Successful build.


Additional info:
Strangely, mock can build 32-bit RHEL6 packages, but not RHEL5 or F18 targets. 64-bit packages build successfully on F18 targets.

I am attaching the build logs from attempts to build "tar". The "tar" SRPM was taken from the Fedora koji (http://koji.fedoraproject.org/koji/buildinfo?buildID=403823). The first logs are from an attempt to rebuild the SRPM package without modification. The second logs are an attempt to build only a 64-bit package after adding ExclusiveArch.

Comment 1 Michael Cronenworth 2013-04-26 16:47:00 UTC
I manually kicked off mock on the host and it fails with a different error message:
DEBUG: ccache: FATAL: Could not find compiler "gcc" in PATH

I chrooted in to the build root and noticed the /usr/bin/ld link is not being created. The binutils package is installed. I'm not sure why the ld link is not being created. After manually creating it I can successfully compile.

On another Fedora 18 system I can use mock (with the same .cfg) to build the package successfully. Both systems use XFS as their root fs, and 64-bit inodes were defaulted on in F18, so that may be a factor.

Comment 2 Michael Cronenworth 2013-08-14 20:01:32 UTC
Upgraded host to Fedora 19. Problem still present.

Comment 3 Miroslav Suchý 2014-11-24 14:30:23 UTC
Do you still experience this bug? I think I was able to reproduce it sever months ago, but I'm not able to reproduce it any more.

Comment 4 Michael Cronenworth 2014-11-24 15:04:05 UTC
Yep, I'm still seeing this. (mock-1.1.41-3.fc19.noarch, kernel-3.14.22-100.fc19.x86_64)

Comment 5 Fedora End Of Life 2015-01-09 17:50:57 UTC
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 6 Miroslav Suchý 2015-01-12 21:04:30 UTC
Is it possible that you have on host machine (that one which run mock) file:
  /etc/rpm/platform
?

Comment 7 Michael Cronenworth 2015-01-12 21:48:36 UTC
I do not have that file.

http://fpaste.org/168837/42109912/

The host is being retired some time later this year so I may not have this box to continue debugging with.

Comment 8 Fedora End Of Life 2015-02-17 14:56:16 UTC
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
bug.

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

Comment 9 Michael Cronenworth 2015-06-09 16:49:46 UTC
Unfortunately I have had to keep the box going.

Upgraded to Fedora 20 but the result is still the same as previous Fedora's.

mock-1.2.7-1.fc20.noarch
koji-1.9.0-10.fc20.gitcd45e886.noarch

Comment 10 Fedora End Of Life 2015-06-29 11:51:43 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
bug.

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.