From: Peter Stephenson <Peter.Stephenson@csr.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: #include problem for generated files included in system.h
Date: Mon, 9 May 2011 11:44:02 +0100 [thread overview]
Message-ID: <20110509114402.38f33fd3@pwslap01u.europe.root.pri> (raw)
Next problem found by compiling somewhere I haven't done for a while.
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.
I could copy or link (but we have systems where either hard links or
soft links don't work) system.h into the build tree if it's different,
but that's not very nice.
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.
--
Peter Stephenson <pws@csr.com> Software Engineer
Tel: +44 (0)1223 692070 Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
next reply other threads:[~2011-05-09 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 10:44 Peter Stephenson [this message]
2011-05-09 14:25 ` Bart Schaefer
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=20110509114402.38f33fd3@pwslap01u.europe.root.pri \
--to=peter.stephenson@csr.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).