I assume this is an upstream problem. Link error: i686-pc-linux-gnu-gcc -rdynamic -L/usr/local/lib -o vim objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/fileio.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/hashtab.o objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o objects/memfile.o objects/memline.o objects/menu.o objects/message.o objects/misc1.o objects/misc2.o objects/move.o objects/mbyte.o objects/normal.o objects/ops.o objects/option.o objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/quickfix.o objects/regexp.o objects/screen.o objects/search.o objects/spell.o objects/syntax.o objects/tag.o objects/term.o objects/ui.o objects/undo.o objects/window.o objects/if_perl.o objects/if_perlsfio.o objects/if_python.o objects/py_config.o objects/netbeans.o objects/version.o -lnsl -lcurses -lgpm -rdynamic -L/usr/local/lib /usr/lib/perl5/5.8.8/i686-linux/auto/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.8/i686-linux/CORE -lperl -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc -L/usr/lib/python2.5/config -lpython2.5 -ldl -lutil -lm -Xlinker -export-dynamic /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function `posix_tmpnam': ./Modules/posixmodule.c:6852: warning: the use of `tmpnam' is dangerous, better use `mkstemp' /usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function `posix_tempnam': ./Modules/posixmodule.c:6805: warning: the use of `tempnam' is dangerous, better use `mkstemp' objects/if_python.o: In function `Python_RestoreThread': /var/tmp/paludis/app-editors/vim-7.0.235/work/vim7/src/if_python.c:421: undefined reference to `PyGILState_Ensure' objects/if_python.o: In function `Python_SaveThread': /var/tmp/paludis/app-editors/vim-7.0.235/work/vim7/src/if_python.c:407: undefined reference to `PyGILState_Release' objects/if_python.o: In function `Python_Init': /var/tmp/paludis/app-editors/vim-7.0.235/work/vim7/src/if_python.c:490: undefined reference to `PyEval_InitThreads' collect2: ld returned 1 exit status feynman portage # paludis --info paludis 0.22.2 Built by root@feynman on 2007-04-09T20:06:58-0500 CXX: i686-pc-linux-gnu-g++ 4.1.2 (Gentoo 4.1.2) CXXFLAGS: -O2 -march=i686 -pipe -ggdb LDFLAGS: DATADIR: /usr/share LIBDIR: /usr/lib LIBEXECDIR: /usr/libexec SYSCONFDIR: /etc stdlib: GNU libstdc++ 20070214 libebt: 1.3.0 libwrapiter: 1.0.0 sandbox: enabled Repository virtuals: Configuration information: format: virtuals Repository installed_virtuals: Configuration information: format: installed_virtuals Repository gentoo: Configuration information: buildroot: /var/tmp/paludis cache: /usr/portage/metadata/cache distdir: /usr/portage/distfiles eclassdirs: /usr/portage/eclass format: ebuild location: /usr/portage names_cache: /var/cache/paludis/.cache/gentoo-names newsdir: /usr/portage/metadata/news pkgdir: /usr/portage/packages profiles: /usr/portage/profiles/default-linux/x86/2006.1 securitydir: /usr/portage/metadata/glsa setsdir: /usr/portage/sets sync: rsync://rsync.us.gentoo.org/gentoo-portage/ sync_options: write_cache: /var/empty Package information: app-admin/eselect-compiler: (none) dev-java/java-config: 1.3.7, 2.0.31-r7 dev-lang/python: 2.4.4, 2.5.1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: (none) dev-util/confcache: (none) sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 Variable information: ACCEPT_KEYWORDS: AUTOCLEAN: CBUILD: i686-pc-linux-gnu CFLAGS: -O2 -march=i686 -pipe -ggdb CHOST: i686-pc-linux-gnu CONFIG_PROTECT: CONFIG_PROTECT_MASK: CTARGET: CXXFLAGS: -O2 -march=i686 -pipe -ggdb DISTDIR: /usr/portage/distfiles FEATURES: GENTOO_MIRRORS: INSTALL_MASK: LANG: LC_ALL: LDFLAGS: LINGUAS: MAKEOPTS: -j3 PKGDIR: PORTAGE_COMPRESS: PORTAGE_COMPRESS_FLAGS: PORTAGE_RSYNC_EXTRA_OPTS: PORTAGE_RSYNC_OPTS: PORTAGE_TMPDIR: /var/tmp/paludis PORTDIR: /usr/portage PORTDIR_OVERLAY: SYNC: USE: Repository installed: Configuration information: buildroot: /var/tmp/paludis format: vdb location: /var/db/pkg names_cache: /var/cache/paludis/.cache/installed-names provides_cache: /var/cache/paludis/.cache/installed-provides root: / world: /var/db/pkg/world Repository local_overlay: Configuration information: buildroot: /var/tmp/paludis cache: /var/empty distdir: /usr/portage/distfiles eclassdirs: /usr/portage/eclass format: ebuild location: /usr/local/portage names_cache: /var/empty newsdir: /usr/local/portage/metadata/news pkgdir: /usr/local/portage/packages profiles: /usr/portage/profiles/default-linux/x86/2006.1 securitydir: /usr/local/portage/metadata/glsa setsdir: /usr/local/portage/sets sync: sync_options: write_cache: /var/empty
Hey Grant! Yeah, I'll also assume it's an upstream issue. I've put block against USE="python" and python-2.5 in the vim eclass. Would you mind filing an upstream bug report about this? Here's their instructions for filing a bug report: 2.6. Where can I report bugs? First collect the required information using the following command: :source $VIMRUNTIME/bugreport.vim Now send the resulting text from the above command to the bugs@vim.org e-mail address. The Vim Development mailing list (see above) is a good place to discuss general bugs. If the bug you find is with syntax highlighting or some other "added feature" (i.e. not directly programmed into vim), attempt to inform the maintainer of that feature. For more information, read :help bug-reports I'm going to close this as UPSTREAM for now. When a patch is made to fix this, I'll make a new gentoo release of vim.
Not related to python-2.5 but instead happens when python is build with USE=-threads (new USE flag in 2.3.6-r1, 2.4.4-r2 and 2.5.1).
(In reply to comment #2) > Not related to python-2.5 but instead happens when python is build with > USE=-threads (new USE flag in 2.3.6-r1, 2.4.4-r2 and 2.5.1). Ah, so it is. Rebuilding python with USE=threads worked perfectly. Is this a known problem upstream?
Ok, I've removed the block in the eclass. Sorry, I've been a little bug-happy the past few days, trying to get caught up after a few months of slacking... So, is there anything that I should be doing for vim? Or is this just a python problem?
It looks like python-2.5.1-r1 will build with threading by default, so a check on the that USE=nothreads wasn't used w/ python should suffice.
