public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at ikkoku dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/95005] New: zstd.h not found if installed in non-system prefix
Date: Fri, 08 May 2020 10:42:34 +0000 [thread overview]
Message-ID: <bug-95005-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95005
Bug ID: 95005
Summary: zstd.h not found if installed in non-system prefix
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at ikkoku dot de
Target Milestone: ---
Created attachment 48482
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48482&action=edit
Add zstd include directory
While adding GCC 10.1.0 to Spack, I ran into a problem with zstd: When
specifying a non-system prefix with --with-zstd (Spack installs each package in
its own prefix), the build of lto-compress.o failed because it could not find
the zstd.h header.
The attached patch fixes the problem. It should probably be changed to export
the appropriate compiler flag from configure.ac to avoid the ifeq in the
Makefile. However, I wanted to avoid touching configure.ac so we do not have to
regenerate configure.
next reply other threads:[~2020-05-08 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 10:42 gcc at ikkoku dot de [this message]
2020-05-09 7:06 ` [Bug bootstrap/95005] " marxin at gcc dot gnu.org
2020-05-11 7:18 ` marxin at gcc dot gnu.org
2020-05-11 8:40 ` gcc at ikkoku dot de
2020-05-11 9:31 ` marxin at gcc dot gnu.org
2020-05-11 9:49 ` marxin at gcc dot gnu.org
2020-05-12 10:49 ` gcc at ikkoku dot de
2020-05-13 13:26 ` marxin at gcc dot gnu.org
2020-05-20 19:35 ` gcc at ikkoku dot de
2020-05-20 22:29 ` egallager at gcc dot gnu.org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2021-05-04 16:48 ` egallager 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-95005-4@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).