Summary: | devel/pcre 8.42 not linked with libz or libbz2 on 12.0 beta 2 | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Dennis Clarke <dclarke> |
Component: | Individual Port(s) | Assignee: | Kirill Ponomarev <krion> |
Status: | Closed Works As Intended | ||
Severity: | Affects Many People | CC: | diizzy, w.schwarzenfeld |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(krion) |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Dennis Clarke
2018-10-30 18:31:58 UTC
Yeah, there is no configure option in port to specify libz support, as it requires zlib.h IIRC, so configure finds zlib.h in your /usr/include but doesn't link pcregrep. Do you want to have pcregrep support with libz to handle .gz files in port? (In reply to Kirill Ponomarev from comment #1) Let me go back and review my own package builds in the Solaris world and see what the justification is. I had always assumed that libz was a defacto standard requirement as well as libbz2. Please hold .. technical crews are investigating ... [insert hold music here] (In reply to Kirill Ponomarev from comment #1) So that is a yes to : Link pcregrep with libz ......... : yes Link pcregrep with libbz2 ....... : yes These are the options but generally libreadline is the default: Link pcretest with libedit ...... : no Link pcretest with libreadline .. : yes Hope that seems reasonable. (In reply to Dennis Clarke from comment #3) Did you explicitly added --enable-pcregrep-libz to build it or it's configure run with default options? (In reply to Kirill Ponomarev from comment #4) My config : ./configure --enable-dependency-tracking --enable-pcre16 --enable-utf \ --enable-unicode-properties --enable-pcre32 --enable-pcregrep-libz \ --enable-pcregrep-libbz2 --enable-pcretest-libreadline --enable-shared \ --enable-static --with-link-size=4 --disable-stack-for-recursion \ --with-pcregrep-bufsize=65536 --without-gnu-ld so .. there we see it. Status? Kirill, is this something we should enable? (In reply to Daniel Engberg from comment #7) Not really Closing this for now as it's not a "bug" and port is working as expected |