From: Peter Stephenson <Peter.Stephenson@csr.com>
To: <zsh-users@zsh.org>
Subject: Re: zsh and the intel fortran compiler
Date: Thu, 29 Mar 2012 17:00:48 +0100 [thread overview]
Message-ID: <20120329170048.5433ca93@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <87bonf1n44.fsf@ft.bewatermyfriend.org>
On Thu, 29 Mar 2012 16:46:19 +0200
Frank Terbeck <ft@bewatermyfriend.org> wrote:
> We (the debian zsh packaging team) just had a bug report from someone
> having rather odd troubles with auto-loadable functions. Turns out, that
> the user has got the intel fortran compiler installed which apparently
> uses $FPATH, too. Complete information about the problem can be found
> here:
>
> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666168>
>
> Does anybody use that compiler, too, and has a workaround for that?
>
> Should we document the issue somewhere (possibly in the README)?
It should be possible to set and restore FPATH locally around where the
compiler is using it; so long as you aren't using shell functions the
shell shouldn't be worried. It would be nice for someone to try this so
we can illustrate the solution.
Other shells will have the same problem; the difference may be they
don't tend to supply as many functions that are supposed to work out of
the box, though there are enough functions around that doesn't seem like
much of a difference.
pws
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
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog
prev parent reply other threads:[~2012-03-29 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 14:46 Frank Terbeck
2012-03-29 16:00 ` Peter Stephenson [this message]
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=20120329170048.5433ca93@pwslap01u.europe.root.pri \
--to=peter.stephenson@csr.com \
--cc=zsh-users@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).