On Mar 29, 2012, at 21:59, Frank Terbeck <f...@bewatermyfriend.org> wrote:
> Hong Xu wrote:
>> On 03/29/2012 09:18 PM, Frank Terbeck wrote:
> [...]
>>> print -l $fpath
>>> c=( ${^fpath}/compinit(N.) )
>>> (( $#c ))&& ls -l $c[1] || echo compinit not found
> [...]
>> It cames up with:
>>
>> /opt/intel/composerxe-2011.5.220/mkl/include
>> compinit not found
>
> I have no idea were this is coming from. Please do this:
>
> % zsh -f
> (and in that new shell)
> % print -l $fpath
>
> If that yields "/opt/intel/composerxe-2011.5.220/mkl/include" then that
> is not from our package. That would be completely broken.
>
>>> In case it's broken try this:
>>>
>>> % zsh -f
>>> (and in that new shell)
>>> % autoload -Uz compinit
>>> % compinit
>>> % print ${#_comps}
>>>
>>> The `compinit' call should *not* fail and the `print' call should return
>>> an integer in the range of slightly above one thousand.
>>
>> compinit fails, and the print gives 0.
>
> This makes me think that your zsh is actually entire broken, what source
> are you getting your package from? Do:
>
> % apt-cache policy zsh
>
> The unchanged $fpath from a default zsh installation on a recent debian
> sid system should look like this:
>
> [...]
>
> In particular, we do NOT have any /opt/intel/... paths in there.
>
I know what's going on here now: intel compiler init scripts change the fpath
variable.
Thanks!
Hong
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
