public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105527] configure option --with-zstd is not documented
Date: Tue, 24 May 2022 11:33:59 +0000 [thread overview]
Message-ID: <bug-105527-4-EXe2VDBsHM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105527-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105527
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:394ff2fbfc84eb6d6cfc56b04e28ee9b42a5ab57
commit r12-8412-g394ff2fbfc84eb6d6cfc56b04e28ee9b42a5ab57
Author: Bruno Haible <bruno@clisp.org>
Date: Wed May 11 17:10:07 2022 +0200
Extend --with-zstd documentation
The patch that was so far added for documenting --with-zstd is pretty
minimal:
- it refers to undocumented options --with-zstd-include and
--with-zstd-lib;
- it suggests that --with-zstd can be used without an argument;
- it does not clarify how this option applies to cross-compilation.
How about adding the same details as for the --with-isl,
--with-isl-include, --with-isl-lib options, mutatis mutandis? This patch
does that.
PR other/105527
gcc/ChangeLog:
* doc/install.texi (Configuration): Add more details about
--with-zstd.
Document --with-zstd-include and --with-zstd-lib
Signed-off-by: Bruno Haible <bruno@clisp.org>
(cherry picked from commit 3677eb80b683cead7db972bc206fd2e75d997bd2)
next prev parent reply other threads:[~2022-05-24 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 22:18 [Bug other/105527] New: " bruno at clisp dot org
2022-05-09 6:59 ` [Bug other/105527] " marxin at gcc dot gnu.org
2022-05-11 12:02 ` cvs-commit at gcc dot gnu.org
2022-05-11 12:06 ` marxin at gcc dot gnu.org
2022-05-11 14:04 ` bruno at clisp dot org
2022-05-11 14:09 ` marxin at gcc dot gnu.org
2022-05-12 7:02 ` marxin at gcc dot gnu.org
2022-05-24 11:24 ` cvs-commit at gcc dot gnu.org
2022-05-24 11:33 ` cvs-commit at gcc dot gnu.org
2022-05-24 11:33 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-24 11:34 ` marxin at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-105527-4-EXe2VDBsHM@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).