Re: [PATCH v2] configure: Support --with-zstd=PATH
Project / Subsystem
binutils / configure
Date
2026-09-29
Proposer
Simon Marchi <simark@simark.ca>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Using a custom `--with-zstd=PATH` offers direct control over library and header locations but might be redundant if `pkg-config` adequately serves the purpose.
- • GCC's approach with separate include/lib path options provides finer control but adds complexity to the configure script.
All attributes
- project
- binutils
- subsystem
- configure
- patch_id
- —
- discussion_id
- 7e7d11d7-8b43-4150-81cb-29864763f4cf@simark.ca
- source_type
- public_inbox
- title
- Re: [PATCH v2] configure: Support --with-zstd=PATH
- headline
- configure: Support --with-zstd=PATH
- tldr
- Questions the use of custom path handling for Zstd in configure scripts when pkg-config might suffice.
- proposer
- Simon Marchi <simark@simark.ca>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Using a custom `--with-zstd=PATH` offers direct control over library and header locations but might be redundant if `pkg-config` adequately serves the purpose.
- • GCC's approach with separate include/lib path options provides finer control but adds complexity to the configure script.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • configure
- • zstd
- • build
- • dependency
- bugzilla_url
- —
- date
- 2026-09-29T00:00:00.000Z
Re: [PATCH v2] configure: Support --with-zstd=PATH
This discussion questions the necessity of custom --with-zstd=PATH logic in binutils’ configure scripts, suggesting that pkg-config could achieve a similar result. The commenter notes that GCC’s --with-zstd is more flexible, allowing separate specification of include and library paths, and is implemented via open-coded logic in configure.ac rather than a generalized approach. The core of the question is about the use case for binutils’ specific path handling.