zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: pws-12
Date: Mon, 15 Mar 1999 12:24:12 +0100	[thread overview]
Message-ID: <9903151124.AA58331@ibmth.df.unipi.it> (raw)
In-Reply-To: "Peter Stephenson"'s message of "Sat, 13 Mar 1999 16:00:01 NFT." <9903131501.AA34131@ibmth.df.unipi.it>

Peter Stephenson wrote:
> I have discovered some problems when the build directory is in a different
> place from the source directory: notably, some files such as modules-bltin,
> signames.c and sigcount.h are created in the source directory instead of
> the build directory, so the first cannot be found and all of them conflict
> with any other build going on in any other directory.  (And I didn't even
> know build was a noun.)

It looks like this was a VPATH feature I've noticed before.  If you've
produce the files signames.c, modules-bltin etc. in the main Src directory,
and VPATH is set to that, it will insist on overwriting those files.
Anyway, I've tried again with a clean source hierarchy and it built
flawlessly in another directory.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  parent reply	other threads:[~1999-03-15 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-13 15:00 pws-12 Peter Stephenson
1999-03-14  5:04 ` BUG: 3.1.5-pws-11 completion coredumps Geoff Wing
1999-03-14  6:14   ` Bart Schaefer
1999-03-14  7:15     ` Geoff Wing
1999-03-15  7:39 ` pws-12 Andrej Borsenkow
1999-03-15 10:52 ` _pdf needs updating Bruce Stephens
1999-03-15 11:24 ` Peter Stephenson [this message]
1999-03-15 11:42 ` _tar uses _multi_parts Bruce Stephens

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=9903151124.AA58331@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).