From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29199-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 9314 invoked by alias); 9 May 2011 14:25:54 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 29199
Received: (qmail 2688 invoked from network); 9 May 2011 14:25:38 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
	autolearn=ham version=3.3.1
Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <110509072517.ZM19256@torch.brasslantern.com>
Date: Mon, 09 May 2011 07:25:16 -0700
In-reply-to: <20110509114402.38f33fd3@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <Peter.Stephenson@csr.com>
 "#include problem for generated files included in system.h" (May  9, 11:44am)
References: <20110509114402.38f33fd3@pwslap01u.europe.root.pri>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: #include problem for generated files included in system.h
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

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.

--