Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 87875

Summary: app-editors/vim-6.3.068 fails to build
Product: Gentoo Linux Reporter: fbusse
Component: New packagesAssignee: Vim Maintainers <vim>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: 2005.0   
Hardware: All   
OS: All   
Whiteboard:
Package list:
Runtime testing required: ---

Description fbusse 2005-04-04 00:52:19 UTC
objects/if_perl.o(.text+0x5cb2): In function `boot_VIM':
: undefined reference to `Perl_Gthr_key_ptr'
objects/if_perl.o(.text+0x5cc4): In function `boot_VIM':
: undefined reference to `Perl_Tstack_base_ptr'
objects/if_perl.o(.text+0x5cd5): In function `boot_VIM':
: undefined reference to `Perl_Gthr_key_ptr'
objects/if_perl.o(.text+0x5ce7): In function `boot_VIM':
: undefined reference to `Perl_Tstack_sp_ptr'
objects/if_perl.o(.text+0x5cf5): In function `boot_VIM':
: undefined reference to `Perl_Gthr_key_ptr'
objects/if_perl.o(.text+0x5d07): In function `boot_VIM':
: undefined reference to `Perl_Tstack_base_ptr'
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make[1]: Leaving directory `/var/tmp/portage/vim-6.3.068/work/vim63/src'
make: *** [first] Error 2

!!! ERROR: app-editors/vim-6.3.068 failed.
!!! Function src_compile, Line 468, Exitcode 2
!!! emake failed

gvim fails in a similiar way.
vim-core was built just fine.


System uname: 2.6.11.6 i686 AMD Athlon(TM) XP 2600+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb  7 2005, 18:56:09)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.7.9-r1, 1.5, 1.6.3, 1.8.5-r3, 1.4_p6, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="-O3 -march=athlon-xp -pipe"
Comment 1 fbusse 2005-04-05 00:43:20 UTC
OK, the problem is perl with "ithreads".
Comment 2 Ciaran McCreesh 2005-04-05 10:55:47 UTC
Looks like basically the same issue as bug 18129. It should generally work if you rebuild perl and libperl with identical USE flags.

*** This bug has been marked as a duplicate of 18129 ***