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 988856 - crash-devel should require lzo-devel etc.
Summary: crash-devel should require lzo-devel etc.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: crash
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dave Anderson
QA Contact: Guangze Bai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-26 14:56 UTC by Frank Ch. Eigler
Modified: 2019-02-19 21:41 UTC (History)
3 users (show)

Fixed In Version: crash-7.0.1-4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-03 07:45:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2013-07-26 14:56:49 UTC
crash/defs.h in 7.0+ includes a hard-coded

#define LZO
#ifdef LZO
#include <lzo/lzo1x.h>
#endif

and the same for something called SNAPPY

So those are de-facto prerequisites of crash-devel, yet are not listed as such.
So when a crash-devel-user's autoconf tests crash/defs.h usability, it
fails in a sad, tragic, and frankly tear-jerking fashion.  Please either add the
Requires:, or else drop the unconditional #define's.

Comment 1 Dave Anderson 2013-07-26 15:06:07 UTC
Thanks Frank.

The base package has:

  BuildRequires: ncurses-devel zlib-devel lzo-devel bison snappy-devel
  Requires: binutils

The crash-devel package has:

  %package devel
  Requires: %{name} = %{version}, zlib-devel

Should the lzo-devel and snappy-devel be added to the crash-devel
Requires line?  And if so, why don't the ncurse-devel and bison
additions also cause a problem?

Comment 3 Dave Anderson 2013-07-26 15:10:43 UTC
Never mind bison and ncurses-devel -- those are for building crash whereas
the lzo-devel and snappy-devel packages are (new) run-time functionality.

But please confirm that you're referencing the crash-devel Requires line
and not the base package Requires line.

Comment 4 Frank Ch. Eigler 2013-07-26 15:47:38 UTC
I do mean the crash-devel requires line, since it's the header file that requires other header files.

(A buildrequires from the base package wouldn't help crash-devel users anyway, as we're not trying to build crash.)


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