Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

.pyenv/libexec/pyenv line 43: cd: xxx.py: Not a directory #807

Closed
changsijay opened this issue Jan 13, 2017 · 2 comments
Closed

.pyenv/libexec/pyenv line 43: cd: xxx.py: Not a directory #807

changsijay opened this issue Jan 13, 2017 · 2 comments

Comments

@changsijay
Copy link

changsijay commented Jan 13, 2017 •
edited by yyuu

$ cat test1.py

#!/usr/bin/env python
print("hello")

$ chmod +x test1.py
$ ln -s test1.py test2
$ ./test2

/home/csj/.pyenv/libexec/pyenv: line 43: cd: test1.py: Not a directory
hello
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40933942-pyenv-libexec-pyenv-line-43-cd-xxx-py-not-a-directory?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github).
@changsijay changsijay changed the title line 43: cd: xxx.py: Not a directory .pyenv/libexec/pyenv line 43: cd: xxx.py: Not a directory Jan 13, 2017
@jonganc
Copy link

jonganc commented Sep 19, 2017 •
edited

Note: this is addressed (though not fixed/merged) in #689.
There, they point to a workaround: run ./configure && make in pyenv's src dir (i.e. $PYENV_ROOT/src, usually ~/.pyenv/src), which will generate libexec/pyenv-realpath.dylib and work around the issue.

@blueyed
Copy link
Contributor

blueyed commented Sep 19, 2018

Closing as duplicate of #580.

@blueyed blueyed closed this as completed Sep 19, 2018
chrisbra added a commit to chrisbra/vim that referenced this issue Apr 12, 2019
@chrisbra
Switch Travis CI to Xenial
b1092bb 
Changes:
- Change how xvfb is called
  https://docs.travis-ci.com/user/gui-and-headless-browsers/
- install libtool-bin for comiling libvterm
- linking fails for libvterm when using clang and --coverage,
  so disable clang compilation for test_libvterm:

  This seems to be an error, compiling libvterm using clang with coverage
  https://travis-ci.org/vim/vim/jobs/519118820

```
libtool --quiet --mode=link --tag=CC clang -rpath /usr/local/lib -version-info 0:0:0 -o libvterm.la src/encoding.lo src/keyboard.lo src/mouse.lo src/parser.lo src/pen.lo src/state.lo src/termscreen.lo src/unicode.lo src/vterm.lo -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E  --coverage -L/usr/local/lib -Wl,--as-needed
ar: `u' modifier ignored since `D' is the default (see `U')
libtool --quiet --mode=compile --tag=CC clang --coverage -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Wall -Iinclude -std=c99 -Wpedantic -DINLINE="" -o t/harness.lo -c t/harness.c
libtool --quiet --mode=link --tag=CC clang --coverage -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Wall -Iinclude -std=c99 -Wpedantic -DINLINE="" -o t/harness t/harness.lo libvterm.la -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E  --coverage -L/usr/local/lib -Wl,--as-needed
/usr/bin/ld: t/.libs/harness: hidden symbol `llvm_gcda_end_file' in /usr/local/clang-7.0.0/lib/clang/7.0.0/lib/linux/libclang_rt.profile-x86_64.a(GCDAProfiling.c.o) is referenced by DSO
/usr/bin/ld: final link failed: Bad value
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
Makefile:78: recipe for target 't/harness' failed
make[2]: *** [t/harness] Error 1
```

That looks like an error on libclang side, so disable it for now.

Finally test86 fails when compiled with gcc on linux using
``
  -g -O1 -DABORT_ON_INTERNAL_ERROR -DEXITFREE -fsanitize=address -fno-omit-frame-pointer
``

The test fails and quite a bit of leaks are detected when compiled
against libpython2.7

Also noteworthy, it throws an error when running asan_symbolize:

```
/opt/pyenv/libexec/pyenv: line 43: cd: asan_symbolize-3.8: Not a directory
```

which looks in fact like this bug: pyenv/pyenv#807
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@blueyed @changsijay @jonganc