zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Sebastian Gniazdowski <psprint3@fastmail.com>,  zsh-workers@zsh.org
Subject: Re: workers/40626 (commit 6c476c22) causes multiple test failures
Date: Mon, 27 Feb 2017 21:38:05 +0100	[thread overview]
Message-ID: <87bmtnv07m.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20170227200843.GA22186@fujitsu.shahaf.local2> (Daniel Shahaf's message of "Mon, 27 Feb 2017 20:08:43 +0000")

Daniel Shahaf wrote:
> Sebastian Gniazdowski wrote on Mon, Feb 27, 2017 at 10:48:12 -0800:
>> PS. Ah, I probably didn't do make install. Ran Src/zsh, but modules were
>> from /usr/local.
>
> That's precisely why I compile the modules statically...

Here is something that will do the required setup to run zsh with all
its modules from its source repository:

  https://github.com/ft/zsh-test


Regards, Frank
-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925


  reply	other threads:[~2017-02-27 20:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  9:41 Sebastian Gniazdowski
2017-02-27 16:42 ` Bart Schaefer
2017-02-27 18:48   ` Sebastian Gniazdowski
2017-02-27 20:08     ` Daniel Shahaf
2017-02-27 20:38       ` Frank Terbeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-26  0:04 Bart Schaefer
2017-02-26  6:16 ` Daniel Shahaf
2017-02-26 19:42   ` Bart Schaefer
2017-02-27  9:31     ` Sebastian Gniazdowski
2017-02-28  7:45     ` Daniel Shahaf
2017-02-28 16:38       ` Bart Schaefer
2017-02-28 17:03         ` Daniel Shahaf
2017-02-28 19:04           ` Bart Schaefer
2017-02-28 21:51             ` Daniel Shahaf
2017-03-01 15:55               ` Bart Schaefer

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=87bmtnv07m.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=d.s@daniel.shahaf.name \
    --cc=psprint3@fastmail.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).