From: Sam Darwin <samuel.d.darwin@gmail.com>
To: cygwin@cygwin.com
Subject: gnu gcc search path
Date: Mon, 31 Jan 2022 14:04:01 -0600 [thread overview]
Message-ID: <CANEqPjEj0DuG0TocUmz6FWXzqzfETVHLGe_7A35q9nkkZVU44A@mail.gmail.com> (raw)
Hi,
Regarding https://cygwin.com/packages/summary/gcc-g++.html This is a
(perhaps) esoteric question about how gnu gcc should operate. It says at
https://gcc.gnu.org/onlinedocs/cpp/Search-Path.html "By default, the
preprocessor looks for header files included by the quote form of the
directive #include "file" first relative to the directory of the current
file," When building boost C++ libraries on an earlier version of cygwin
this used to work fine. Now, updating to a newer cygwin version on
Appveyor, "APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2019" , it has
broken..
Errors appear such as
"fatal error: zutil.h: No such file or directory 8 | #include "zutil.h"
compilation terminated."
"No such file or directory."
What do you think? It can't find the header file, which happens to be in
the same directory, the current directory. It seems like a bug, however,
if it's intended behavior, and the current directory has been removed from
the search path, then could a command-line flag be provided to optionally
re-enable the previous functionality?
reply other threads:[~2022-01-31 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CANEqPjEj0DuG0TocUmz6FWXzqzfETVHLGe_7A35q9nkkZVU44A@mail.gmail.com \
--to=samuel.d.darwin@gmail.com \
--cc=cygwin@cygwin.com \
/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).