RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 625843 - kmod build fails with latest kmodtool
Summary: kmod build fails with latest kmodtool
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: driver-update-program
Version: 6.0
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Jon Masters
QA Contact: Qian Cai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-20 15:23 UTC by Martin Wilck
Modified: 2010-08-23 22:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-20 20:23:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
mock build log from snapshot 11 (14.99 KB, application/force-download)
2010-08-20 15:23 UTC, Martin Wilck
no flags Details

Description Martin Wilck 2010-08-20 15:23:14 UTC
Created attachment 439973 [details]
mock build log from snapshot 11

Description of problem:
The kmodtool from redhat-rpm-config 9.0.3-25 has the %{_target_cpu} macro removed from paths in various places. That is wrong


Version-Release number of selected component (if applicable):
redhat-rpm-config 9.0.3-25

How reproducible:
always


Steps to Reproduce:
1. build kmod with current kmodtool
  
Actual results:
Build error (bad file list)


Expected results:
No build error


Additional info:
The bad path in %files causes the build error, but I am positive that %{_target_cpu} is missing in paths in various other places.

Comment 2 Jon Masters 2010-08-20 20:23:12 UTC
Can you reproduce this with my ddiskit v2.4 example? I do not see such problems with file lists here on 20100815 (snapshot 12), and my examples are building and working fine on RHEL6 with redhat-rpm-config 9.0.3-25.el6. They install into /lib/modules/2.6.32-63.el6.x86_64 as expected.

Please tell me:

1). What are you building on? Exactly.
2). What are you building? Do you have the SPEC file, or snippet for me?

Jon.

Comment 5 Jon Masters 2010-08-20 21:53:19 UTC
It might be that we need to get you a newer snapshot. Do you expect to receive snapshot 12 and/or 13?

Jon.

Comment 6 Martin Wilck 2010-08-23 08:20:34 UTC
(In reply to comment #5)
> It might be that we need to get you a newer snapshot. Do you expect to receive
> snapshot 12 and/or 13?

Yes, when they're ready for partners.

I was building using mock on a clean snapshot 11 platform. That's the latest I have.

Comment 7 Martin Wilck 2010-08-23 09:25:44 UTC
(In reply to comment #6)

> I was building using mock on a clean snapshot 11 platform. That's the latest I
> have.

That's what I thought I was doing. For some reason mock didn't update the redhat-rpm-config package in the chroot cleanly.

Comment 8 Martin Wilck 2010-08-23 10:02:35 UTC
After re-initializing the mock buildroot, the build went fine. Sorry for the noise.

Comment 9 Jon Masters 2010-08-23 22:20:18 UTC
No problem at all! And thanks, again, for your attention and help, Martin.


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