Summary: | vim 6.3-r2 is using -L/usr/local/lib, and getting the wrong libraries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | hixon_c |
Component: | Current packages | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED WONTFIX | ||
Severity: | minor | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
hixon_c
2004-12-20 19:03:01 UTC
Hrm, is vim the only package that does this? Not sure whether this is a general autoconfism or something strange vim is doing. It looks like the auto-generated configure script tests for the presence of /usr/local/lib and adds it to LDFLAGS if it exists: (snagged from /var/tmp/portage/vim-6.3-r2/work/vim63/src/auto/configure) if test -z "$have_local_lib" -a -d /usr/local/lib; then tt=`echo "$LDFLAGS" | sed -e 's+-L/usr/local/lib ++g' -e 's+-L/usr/local/lib$++g'` if test "$tt" = "$LDFLAGS"; then LDFLAGS="$LDFLAGS -L/usr/local/lib" fi fi Thats as far as I've got in my digging... I don't know autoconf. Is configure.in the master? I haven't _noticed_ any other package trying to link with stuff I have in /usr/local/lib. In my case, the error occurs because of a mismatch of the headers and library: -I/usr/include/python2.3 vs. -L/usr/local/lib. From the above link:
> If vim is built with USE="blah", and the blah library is present in
> /usr/local, vim will link against the /usr/local version. This is
> causing problems for at least one user. On the other hand, I'm thinking
> that this behaviour is probably desirable, in that it allows users to
> link against non-portage-installed apps if the user so desires.
I understand that it might be desirable to link against the /usr/local version,
however it's not doing that correctly either, at least in the case of USE="python". If it's going to use the python in /usr/local,
it should be using the python installed in /usr/local/bin to obtain the
build flags (such as -I/usr/local/include/python2.3).
What seems to be happening with vim is: the configure script notices that /usr/local/lib exists, and adds -L/usr/local/lib to the LDFLAGS, but it's
using the /usr version of python to get the python (module?) build flags (notice the -I/usr/include/python2.3 in my compile output).
I'm going to close this one as WONTFIX. Looks like this is an autoconf feature. WONTFIX |