| Summary: | app-editors/vim-7.1.319 - python undefined reference to `openpty' undefined reference to `forkpty' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jason S. <vxjasonxv> |
| Component: | New packages | Assignee: | Vim Maintainers <vim> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | anthony.giorgio, lars |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jason S.
2008-08-11 05:22:22 UTC
Can you test if vim-7.2 works fine? (In reply to comment #1) > Can you test if vim-7.2 works fine? No dice: OLD_PO_FILE_INPUT=yes msgfmt -v -o uk.cp1251.mo uk.cp1251.po /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function `posix_tempnam': (.text+0x4f5a): warning: the use of `tempnam' is dangerous, better use `mkstemp' /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function `posix_tmpnam': (.text+0x5043): warning: the use of `tmpnam_r' is dangerous, better use `mkstemp' /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function `posix_openpty': (.text+0x22f2): undefined reference to `openpty' /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function `posix_forkpty': (.text+0x2364): undefined reference to `forkpty' collect2: ld returned 1 exit status (In reply to comment #2) > (In reply to comment #1) > > Can you test if vim-7.2 works fine? > > No dice: In my case, 7.2 works fine. No linking error (In reply to comment #2) > (In reply to comment #1) > > Can you test if vim-7.2 works fine? > > No dice: > > OLD_PO_FILE_INPUT=yes msgfmt -v -o uk.cp1251.mo uk.cp1251.po > /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function > `posix_tempnam': > (.text+0x4f5a): warning: the use of `tempnam' is dangerous, better use > `mkstemp' > /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function > `posix_tmpnam': > (.text+0x5043): warning: the use of `tmpnam_r' is dangerous, better use > `mkstemp' > /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function > `posix_openpty': > (.text+0x22f2): undefined reference to `openpty' > /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function > `posix_forkpty': > (.text+0x2364): undefined reference to `forkpty' > collect2: ld returned 1 exit status > Can you please post the USE Flags you have set for dev-lang/python? (In reply to comment #4) > > Can you please post the USE Flags you have set for dev-lang/python? Unfortunately I've rebuilt my computer since my last comment. vim (7.2.108) has successfully installed with the python USE flag enabled. In case it will help what flags I have set now, I'm going to provide vim and python: [ Found these USE variables for dev-lang/python-2.4.4-r13 ] U I + + berkdb : Adds support for sys-libs/db (Berkeley DB for MySQL) - - bootstrap : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during original system bootstrapping [make stage2] - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1 ] - + cxx : Builds support for C++ (bindings, extra libraries, code generation, ...) - - doc : Adds extra documentation (API, Javadoc, etc) - - elibc_uclibc : ELIBC setting for systems that use the uClibc C library - - examples : Install examples, usually source code + + gdbm : Adds support for sys-libs/gdbm (GNU database libraries) + + ipv6 : Adds support for IP version 6 + + ncurses : Adds ncurses support (console display library) + + readline : Enables support for libreadline, a GNU line-editing library that almost everyone wants + + ssl : Adds support for Secure Socket Layer connections + + threads : Adds threads support for various packages. Usually pthreads - - tk : Adds support for Tk GUI toolkit - - ucs2 : Enable byte size 2 unicode (DON'T USE THIS UNLESS YOU KNOW WHAT YOU'RE DOING) - - wininst : Install required Windows executables to create an executable installer for MS Windows. [ Found these USE variables for dev-lang/python-2.5.4-r2 ] U I + + berkdb : Adds support for sys-libs/db (Berkeley DB for MySQL) - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1 ] - - doc : Adds extra documentation (API, Javadoc, etc) - - elibc_uclibc : ELIBC setting for systems that use the uClibc C library - - examples : Install examples, usually source code + + gdbm : Adds support for sys-libs/gdbm (GNU database libraries) + + ipv6 : Adds support for IP version 6 + + ncurses : Adds ncurses support (console display library) + + readline : Enables support for libreadline, a GNU line-editing library that almost everyone wants + + sqlite : Adds support for sqlite - embedded sql database + + ssl : Adds support for Secure Socket Layer connections + + threads : Adds threads support for various packages. Usually pthreads - - tk : Adds support for Tk GUI toolkit - - ucs2 : Enable byte size 2 unicode (DON'T USE THIS UNLESS YOU KNOW WHAT YOU'RE DOING) - - wininst : Install required Windows executables to create an executable installer for MS Windows. + + xml : Add support for XML files [ Found these USE variables for app-editors/vim-7.2.108 ] U I + + acl : Adds support for Access Control Lists + + bash-completion : Enable bash-completion support - - cscope : Enables cscope interface -- in vim for example + + gpm : Adds support for sys-libs/gpm (Console-based mouse driver) - - minimal : Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features) + + nls : Adds Native Language Support (using gettext - GNU locale utilities) + + perl : Adds support/bindings for the Perl language + + python : Adds support/bindings for the Python language + + ruby : Adds support/bindings for the Ruby language + + vim-pager : Install vimpager and vimmanpager links + + vim-with-x : Link console vim against X11 libraries to enable title and clipboard features in xterm Closing, no one can reproduce this, including the original reporter, so I'm not sure how we can run it down. Shouldn't this be closed invalid or the like? Yeah, probably should have been... |
