Ticket #16849 (closed defect: fixed)
bzip2: wrong dylib version number
| Reported by: | ryandesign@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | Cc: | mcalhoun@… | |
| Port: | bzip2 |
Description
bzip2 is at 1.0.5 but patch-Makefile-dylib.diff makes a library with version 1.0.4. We should not be hardcoding the version number in the patch but rather making use of the ${version} variable.
Change History
comment:3 Changed 4 years ago by ryandesign@…
- Cc mcalhoun@… added
Marcus fixed this for Darwin in r46773 but not for other OSes.
I'm still hoping there's a way to combine the existing patchfiles and make a single build process for all operating systems.
comment:4 Changed 4 years ago by ryandesign@…
I wanted to borrow some magic from the zlib Makefile for figuring out the proper shared lib extension and version numbers.
I got stuck on trying to figure out why some of the differences between the .so patch and the .dylib patch exist, and my lack of knowledge of non-Darwin systems in knowing how they like things done.
comment:5 Changed 4 years ago by mcalhoun@…
Unfortunately, I just know the basics of shared libraries on non-Darwin machines
(http://www.linux.org/docs/ldp/howto/Program-Library-HOWTO/shared-libraries.html and
http://linux.die.net/man/1/chrpath).
Anything I tried would be best guess with no way of testing it.


patch-Makefile-so.diff is affected too (it makes a library with version "1.0.2").