From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: #include problem for generated files included in system.h
Date: Mon, 09 May 2011 07:25:16 -0700 [thread overview]
Message-ID: <110509072517.ZM19256@torch.brasslantern.com> (raw)
In-Reply-To: <20110509114402.38f33fd3@pwslap01u.europe.root.pri>
On May 9, 11:44am, Peter Stephenson wrote:
}
} My Solaris 8 (ancient but still working) set-up uses separate source and
} build trees. This is falling over when system.h tries to include
} zshterm.h and zshcurses.h: system.h is included in the build tree from
} the source tree (<somer-relative-path-added-to-zsh.mdd>/system.h) which
} causes it not to find zshterm.h and zshcurses.h in the build tree itself.
Thanks for running into this before I did. ;-) I've used separate source
and build trees for years on my primary zsh test system, because I build
the shell both static and dynamic link from the same source tree.
} I think the fix is probably to move the stuff from system.h into a
} separate header and #include that after system.h. However, maybe
} someone can see a simpler fix.
Rather than generate <some-relative-path-added-to-zsh.mdd>/system.h
why not add -Isome-relative-path-added-to-zsh.mdd to CLFAGS? Is the
path being generated at a poor place relative to building Makefiles?
While we're at it the name "system.h" has always seemed a bit generic
to me, and therefore likely to clash with something.
--
next prev parent reply other threads:[~2011-05-09 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 10:44 Peter Stephenson
2011-05-09 14:25 ` Bart Schaefer [this message]
2011-05-10 16:36 ` Peter Stephenson
2011-05-10 16:45 ` Peter Stephenson
2011-05-10 21:04 ` Alexey I. Froloff
2011-05-11 8:53 ` Peter Stephenson
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=110509072517.ZM19256@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).