Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 161078 - Missing BuildRequires dependency on zlib-devel
Summary: Missing BuildRequires dependency on zlib-devel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openssl096b
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Tomas Mraz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-20 14:16 UTC by Andreas Thienemann
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-20 14:25:47 UTC


Attachments (Terms of Use)

Description Andreas Thienemann 2005-06-20 14:16:10 UTC
During a testbuild of openssl096b-0.9.6b-22.1 in mock, the rebuild process
stops with the following error:

+ gcc -o openssl-thread-test -I./include -O2 -g -pipe -m64 -Wa,--noexecstack
/builddir/build/SOURCES/openssl-thread-test.c lib
ssl.a libcrypto.a -lpthread -lz -ldl
/usr/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
error: Bad exit status from /var/tmp/rpm-tmp.86226 (%build)


Adding zlib-devel to the BuildRequires: list should fix this problem.
Note: This also seems to be an issue in rawhide.

Comment 1 Tomas Mraz 2005-06-20 14:25:47 UTC
I'm sorry but this isn't serious enough for RHEL-4 to fix.

The current openssl/openssl097a packages in rawhide and FC-4 are without this
problem.

There is no openssl096b package in FC-4 or rawhide.


Comment 2 Andreas Thienemann 2005-06-20 14:42:28 UTC
I was looking at
<http://cvs.fedora.redhat.com/viewcvs/rpms/openssl096b/devel/openssl.spec?view=markup>,
which had the same problem.

But if it's not shipped anymore... who cares? ;) 



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