This is the version of vim that I am using
vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 15 2020 06:40:31)
Included patches: 1-2269
Modified by team+vim#tracker.debian.org
Compiled by team+vim#tracker.debian.org
Huge version without GUI. Features included (+) or not (-):
+acl -farsi -mouse_sysmouse -tag_any_white
+arabic +file_in_path +mouse_urxvt +tcl
+autocmd +find_in_path +mouse_xterm +termguicolors
+autochdir +float +multi_byte +terminal
-autoservername +folding +multi_lang +terminfo
-balloon_eval -footer -mzscheme +termresponse
+balloon_eval_term +fork() +netbeans_intg +textobjects
-browse +gettext +num64 +textprop
++builtin_terms -hangul_input +packages +timers
+byte_offset +iconv +path_extra +title
+channel +insert_expand +perl -toolbar
+cindent +job +persistent_undo +user_commands
-clientserver +jumplist +postscript +vartabs
-clipboard +keymap +printer +vertsplit
+cmdline_compl +lambda +profile +virtualedit
+cmdline_hist +langmap -python +visual
+cmdline_info +libcall +python3 +visualextra
+comments +linebreak +quickfix +viminfo
+conceal +lispindent +reltime +vreplace
+cryptv +listcmds +rightleft +wildignore
+cscope +localmap +ruby +wildmenu
+cursorbind +lua +scrollbind +windows
+cursorshape +menu +signs +writebackup
+dialog_con +mksession +smartindent -X11
+diff +modify_fname +sound -xfontset
+digraphs +mouse +spell -xim
-dnd -mouseshape +startuptime -xpm
-ebcdic +mouse_dec +statusline -xsmp
+emacs_tags +mouse_gpm -sun_workshop -xterm_clipboard
+eval -mouse_jsbterm +syntax -xterm_save
+ex_extra +mouse_netterm +tag_binary
+extra_search +mouse_sgr -tag_old_static
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
defaults file: "$VIMRUNTIME/defaults.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fdebug-prefix-map=/build/vim-iU6mZD/vim-8.1.2269=. -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lcanberra -lacl -lattr -lgpm -ldl -L/usr/lib -llua5.2 -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/perl/5.30/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/python3.8/config-3.8-x86_64-linux-gnu -lpython3.8 -lcrypt -lpthread -ldl -lutil -lm -lm -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lm -lruby-2.7 -lm
This is my vimrc
.vimrc
set nocompatible
set incsearch
set hlsearch
set number relativenumber
set encoding=utf-8
set noswapfile
set smartindent
set undodir=~/.vim/undodir
set undofile
let mapleader = " "
syntax enable
filetype plugin indent on
set path+=**
set wildmenu
let $RTP=split(&runtimepath,',')[0]
let $RC="$HOME/.vimrc"
" Ctrl-[ for finding definition
command! MakeTags !ctags -R .
augroup numbertoggle
autocmd!
autocmd BufEnter,FocusGained,InsertLeave * set relativenumber
autocmd BufLeave,FocusLost,InsertEnter * set norelativenumber
augroup END
" Plugins will be downloaded under the specified directory.
call plug#begin('~/.vim/plugged')
" Declare the list of plugins.
Plug 'tpope/vim-sensible'
Plug 'tpope/vim-surround'
Plug 'tpope/vim-repeat'
Plug 'junegunn/seoul256.vim'
Plug 'preservim/nerdtree'
Plug 'ap/vim-css-color'
Plug 'ajmwagar/vim-deus'
Plug 'dbeniamine/cheat.sh-vim'
Plug 'valloric/youcompleteme'
Plug 'powerline/powerline' , {'rtp': 'powerline/bindings/vim/'}
" List ends here. Plugins become visible to Vim after this call.
call plug#end()
set guifont=Source\ Code\ Pro\ for\ Powerline
set background=dark " Setting dark mode
colorscheme deus
I would like to fix this Error such that the correct Characters are displayed I am using vim not gvim and I tried to add a font but it didn't work.
What I am doing wrong?
This answer is for everyone, who wants to install powerline only in vim in the windows terminal (using wsl Ubuntu 20.04). It took me quite some time.
The reason why I had this issue was that glyphs where missing in the windows terminal font. I tried to install the powerline fonts according to the documentation(https://powerline.readthedocs.io/en/latest/installation/linux.html#fontconfig) as #romainl suggested but that didn't work. Furthermore I tried to install all powerline fonts from the github(https://github.com/powerline/fonts), I ran both the installation scripts. The one for windows in the powershell console according to this blog() and the one for Linux on the Ubuntu WSL Machine according to the documentation. Didn't work either.
Then I stumbled upon a blog post of Microsoft(https://learn.microsoft.com/en-us/windows/terminal/tutorials/powerline-setup), where the person installed a theming framework oh-my-posh. However, I neither wanted to install a theming framework nor a special version of git. Furthermore I only wanted to install powerline in vim not in my whole console. This was the moment when I asked myself: did I miss something? And indeed I did catch a little detail. The answer was to install a the Cascadia Mono PL font (https://github.com/microsoft/cascadia-code/releases) which includes the missing glyphs. Just download the zip and double click on the font. Furthermore I had to set the fontface in the setting.json of the windows terminal (which can open with pressing (CTRL + ,) in the terminal). Your settings should look something like this:
{
"guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
"hidden": false,
"name": "Ubuntu-20.04",
"fontFace": "Cascadia Code PL",
"padding" : "0, 0, 0, 0",
"source": "Windows.Terminal.Wsl"
},
Now that the prerequisites are handled, I can talk about the correct settings you need to set in your .vimrc in order to use powerline in vim. First of all you should use a plugin manager I would recommend vim-plug(https://github.com/junegunn/vim-plug) simply because it is maintained and I use it. After installing vim-plug you only need to add the following one line to your .vimrc between the import statements:
Plug 'powerline/powerline' , {'rtp': 'powerline/bindings/vim/'}
The conclusion is that it doesn't matter how many fonts you install in the wsl machine and you do not need to set the guifont in the windows terminal because it does nothing. This is why the documentation of didn't really help because it missed a little information which I needed to connect the dots.
UPDATE:
Windows changed its font naming, the new name in the new windows terminal settings page is Cascadia Code PL Regular
Related
I am currently following this guide and trying to build my u-boot. The issue I am facing is the following error:
cc1: warning: unknown register name: x18
cc1: error: bad value (‘armv8-a’) for ‘-march=’ switch
This occurs when I run sudo make O=p3450-000 in my terminal.
I have researched this error however, I feel as those I have properly set my CROSS_COMPILE variable. The following is my GCC version when I run arm-linux-gnueabi-gcc -v:
Using built-in specs.
COLLECT_GCC=arm-linux-gnueabi-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc-cross/arm-linux-gnueabi/7/lto-wrapper
Target: arm-linux-gnueabi
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm --disable-libquadmath --disable-libquadmath-support --enable-plugin --with-system-zlib --with-target-system-zlib --enable-multiarch --enable-multilib --disable-sjlj-exceptions --with-arch=armv5t --with-float=soft --disable-werror --enable-multilib --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=arm-linux-gnueabi --program-prefix=arm-linux-gnueabi- --includedir=/usr/arm-linux-gnueabi/include
Thread model: posix
gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)
I set my CROSS_COMPILE variable by trying the following commands:
CROSS_COMPILE=$HOME/l4t-gcc/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
export CROSS_COMPILE=$HOME/l4t-gcc/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
Neither seem to work.
Edit: Using CROSS_COMPILE in my make command seems to have worked.
I try to install the newest version of vim on Red Hat 6.6.
I use the script below to run configure:
# change to folder where vim sources are
cd ~/vim
# here I compiled newest version of libuuid.
LIBDIR="/home/muellc1b/uuid/lib"
export LD_LIBRARY_PATH=$LIBDIR:$LD_LIBRARY_PATH # prepend to path
export LDFLAGS="-L$LIBDIR"
#export LIBS="-llibuuid.so"
./configure \
--prefix=/home/muellc1b/vim_installation
#LIBS="-l$LIBDIR" \
#LDFLAGS="-L$LIBDIR"
When trying to run the makefile, I get the following errors:
gcc -L/home/muellc1b/uuid/lib -L/usr/local/lib -Wl,--as-needed [...] -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lSM -lICE -lXt -lX11 -lSM -lICE -lm -ltinfo -lelf -lnsl -lselinux -lacl -lattr -lgpm
/usr/lib/../lib64/libSM.so: undefined reference to `uuid_unparse_lower#UUID_1.0'
/usr/lib/../lib64/libSM.so: undefined reference to `uuid_generate#UUID_1.0'
collect2: error: ld returned 1 exit status
Can someone point me to a solution on how to correctly link my custom library?
As I saw, you got a satisfactory answer here where the solution was to run the configure script normally, open src/auto/config.mk, and change the line X_PRE_LIBS = -lSM -lICE -lXpm to X_PRE_LIBS = -luuid -lSM -lICE -lXpm. Then do make.
I had exactly the same error message, but when compiling PCL (point cloud library). The error had a different cause and different solution. I'll add it here, as this page came up when looking for solution - perhaps it will help someone.
My problem was that when doing cmake .. before make it gave warnings like this:
CMake Warning at cmake/pcl_targets.cmake:194 (add_library):
Cannot generate a safe runtime search path for target pcl_io because
files in some directories may conflict with libraries in implicit directories:
All the directories that were referenced were under anaconda3/lib. I ignored it and make gave me the same error libSM.so: undefined reference to `uuid_unparse_lower#UUID_1.0' and some more :). The solution was to remove anaconda lib folder from the path, and build again. In detail:
delete build directory and create it again
echo $PATH and look for anaconda lib directory
Copy the PATH output from previous step and remove reference to anaconda folder
execute PATH=[MODIFIED_PATH] where [MODIFIED_PATH] is the result from previous step
Execute echo $PATH again to see that anaconda directory has been removed
build the project again in the same terminal window
Now the process uses system libraries, not the anaconda ones and compilation succeeds.
An example of modified PATH: if the original was /home/you/anaconda3/bin:/usr/local/bin:/usr/sbin:/usr/bin then the modified one is /usr/local/bin:/usr/sbin:/usr/bin
NB! You probably do not want to change the PATH permanently (your anaconda installation might stop working) that is why it is done from the terminal not from .bashrc file.
I am trying to compile the Terminology terminal emulator (btw this does some very cool things and is work checking out). However the build fails giving me the following error:
/usr/bin/ld: cannot find -lecore_input
After some messing around with using make -n to print the commands being (or would would be) run, I find that the following line is the one that fails:
gcc -g -O2 -o terminology terminology-about.o terminology-col.o terminology-config.o terminology-controls.o terminology-ipc.o terminology-keyin.o terminology-main.o terminology-media.o terminology-options.o terminology-options_font.o terminology-options_theme.o terminology-options_themepv.o terminology-options_wallpaper.o terminology-options_colors.o terminology-options_behavior.o terminology-options_keys.o terminology-options_helpers.o terminology-options_video.o terminology-sel.o terminology-termio.o terminology-termcmd.o terminology-termiolink.o terminology-termpty.o terminology-termptydbl.o terminology-termptyesc.o terminology-termptyops.o terminology-termptygfx.o terminology-termptyext.o terminology-termptysave.o lz4/terminology-lz4.o terminology-utf8.o terminology-win.o terminology-utils.o terminology-dbus.o terminology-extns.o terminology-app_server.o terminology-app_server_eet.o -lelementary -lm -lefreet_mime -lefreet_trash -ledbus -ldbus-1 -lecore_con -leina -lpthread -leet -levas -lecore -lecore_evas -lecore_file -ledje -lemotion -lecore_input -lecore_imf -lecore_imf_evas -lecore_ipc -lefreet -lethumb_client -leldbus
Running this command on its own from the correct directory and adding the -v option, I get the following output:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-16' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.2 (Debian 4.8.2-16)
COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/
LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-g' '-O2' '-o' 'terminology' '-mtune=generic' '-march=x86-64'
/usr/lib/gcc/x86_64-linux-gnu/4.8/collect2 --sysroot=/ --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o terminology /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crt1.o /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbegin.o -L/usr/lib/gcc/x86_64-linux-gnu/4.8 -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../.. terminology-about.o terminology-col.o terminology-config.o terminology-controls.o terminology-ipc.o terminology-keyin.o terminology-main.o terminology-media.o terminology-options.o terminology-options_font.o terminology-options_theme.o terminology-options_themepv.o terminology-options_wallpaper.o terminology-options_colors.o terminology-options_behavior.o terminology-options_keys.o terminology-options_helpers.o terminology-options_video.o terminology-sel.o terminology-termio.o terminology-termcmd.o terminology-termiolink.o terminology-termpty.o terminology-termptydbl.o terminology-termptyesc.o terminology-termptyops.o terminology-termptygfx.o terminology-termptyext.o terminology-termptysave.o lz4/terminology-lz4.o terminology-utf8.o terminology-win.o terminology-utils.o terminology-dbus.o terminology-extns.o terminology-app_server.o terminology-app_server_eet.o -lelementary -lm -lefreet_mime -lefreet_trash -ledbus -ldbus-1 -lecore_con -leina -lpthread -leet -levas -lecore -lecore_evas -lecore_file -ledje -lemotion -lecore_input -lecore_imf -lecore_imf_evas -lecore_ipc -lefreet -lethumb_client -leldbus -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-linux-gnu/4.8/crtend.o /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crtn.o
/usr/bin/ld: cannot find -lecore_input
collect2: error: ld returned 1 exit status
Of course libecore_input is installed:
$ sudo updatedb
$ locate ecore_input.so
/usr/lib/x86_64-linux-gnu/libecore_input.so
/usr/lib/x86_64-linux-gnu/libecore_input.so.1
/usr/lib/x86_64-linux-gnu/libecore_input.so.1.7.7
And /usr/lib/x86_64-linux-gnu/ is in both the LIBRARY_PATH in the gcc output and appear as a -L option on the collect2 command.
I also get the same error when I try with gcc-4.7. What has went wrong here? How can I get the program to build?
Update
Since the cause of this was actually a packaging issue, I should have added that I am using Debian Jessie with mixed testing/unstable repositories.
This was caused by /usr/lib/x86_64-linux-gnu/libecore_input.so being a dead link as the result of a Debian packaging issue and the use of mixed testing/unstable repositories.
The /usr/lib/x86_64-linux-gnu/libecore_input.so link was part of the libecore-dev package while the library itself was part of libecore-input1. The installed version of libecore-dev was 1.8.6-1 while libecore-input1 was version 1.7.7. As such the target of the libecore_input.so link was libecore_input.so.1.8.6 which didn't exist. While libecore-dev had versioned dependencies for other libraries, libecore-input1 was an indirect dependency and not properly versioned. This probably a a bug since if a package includes links to a shared library, then its dependencies should make sure that the correct version of the library is installed.
The solution was simply to upgrade the libecore-input package.
Actually I have the impression that the containing folder /usr/lib/x86_64-linux-gnu/ is not contained in the "collect2 command" as you claim when closing your question. Take a close look: it is indeed mentioned in the LD_LIBRARY_PATH (which is not of interest when linking), but it is not mentioned as -L flag in the COLLECT_GCC_OPTIONS output. There is only a folder /usr/lib/gcc/x86_64-linux-gnu/4.8/collect2 in there.
I suggest you change that and retry the linking.
I have mini pc with vortex86DX processor. And today I install Ubuntu 9.04 on it. Now I want to use my program, which use gtk/gtk.h, to display some data. And I have question -
What dependencies have programs, which use GTK 3.0? It's very important for me, because I have not internet access on this small pc.
You generally build such GTK programs using pkg-config. And I am getting (on Debian/Sid/AMD64) the compile flags
% pkg-config --cflags gtk+-x11-3.0
-pthread -I/usr/include/gtk-3.0 -I/usr/include/atk-1.0 \
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/pango-1.0 \
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo \
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 \
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include \
-I/usr/include/harfbuzz -I/usr/include/freetype2 \
-I/usr/include/pixman-1 -I/usr/include/libpng12 \
-I/usr/include/libdrm
and the link flags
% pkg-config --libs gtk+-x11-3.0
-lgtk-3 -lgdk-3 -latk-1.0 -lgio-2.0 -lpangocairo-1.0 \
-lgdk_pixbuf-2.0 -lcairo-gobject -lpango-1.0 -lcairo \
-lgobject-2.0 -lglib-2.0
Notice that these shared libraries link some other ones (eg -lX11 or -ldbus). Try to ldd some GTK binary (e.g. your own one, or gedit)
NB: I have manually added the backslashes and newlines for readability
However, there are much more other runtime dependencies: the X11 server and related things (session and windows managers, fonts and images notably and perhaps even some "desktop" environment à la Gnome or IceWM, etc...).
I suggest installing GTK usig the package system (e.g. using aptitude install on Ubuntu) with a network connection (perhaps using a chroot-ed environment) to understand all the dependencies.
I cloned the vim source using mercurial, and ran the following commands:
make distclean
./configure --with-features=huge
make
sudo make install
The output of all these commands seemed normal.
Yet the output of my vim --version is missing features that should be enabled when ./configure (xterm_clipboard, for example). How can I diagnose this problem? My goal is to enable netbeans_intg.
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Mar 23 2010 12:50:41)
Included patches: 1-315
Modified by <bugzilla#redhat.com>
Compiled by <bugzilla#redhat.com>
Huge version without GUI. Features included (+) or not (-):
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv +cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path
+float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand
+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap
+menu +mksession +modify_fname +mouse -mouseshape +mouse_dec +mouse_gpm
-mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte
+multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra +perl +postscript
+printer +profile +python +quickfix +reltime +rightleft +ruby +scrollbind
+signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse
+textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
-X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save
system vimrc file: "/etc/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/etc"
f-b for $VIMRUNTIME: "/usr/share/vim/vim72"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -g -pipe -Wall -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=1 -D_REENTRANT -D_GNU_SOURCE -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE -I/usr/local/include/python2.6 -pthread -I/opt/local/ruby-1.8.7/lib/ruby/1.8/x86_64-linux
Linking: gcc -L. -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-rpath,/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE -L/usr/local/lib -o vim -lselinux -lncurses -lacl -lgpm -Wl,-E -Wl,-rpath,/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/auto/DynaLoader/DynaLoader.a -L/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE -lperl -lresolv -lutil -lc -L/usr/local/lib/python2.6/config -lpython2.6 -lutil -Xlinker -export-dynamic -lruby-static -lm
Are you sure you're running the vim you built, and not another vim that was already on your system? In any case, that vim was not built with any GUI (X11) support, as you can see by Huge version without GUI in the log.
Including huge doesn't get you every feature; it just gets you a lot of them. If you want X11 and xterm_clipboard, make sure you specify an X11 build option. For a GTK-based system, you can do something like:
./configure --with-features=huge --enable-gui=gtk2
That will get you most of the X11/graphical features. If you're not using GTK2, you'll have to specify something else; check out ./configure --help for a list of features.
You'll need to have various GTK/X11 (or whatever GUI you go with) development libraries installed in order to build with GUI support. It's possible that it's trying to build with X11 support, but you don't have the right libraries. Review your configure output for errors.
Your OS may have a pre-built binary with all the features you need, as others have suggested, but I've found I always end up having to compile it for one thing or another eventually, so it's worth figuring out. If you provide more information about the OS you're running (and if OSX, which supplemental package system), someone may have an OS-specific binary package suggestion.
When you don't have some features enabled in a huge build, that's probably due to missing dependencies. The configure script runs a lot of detections, and skips certain features when the corresponding libraries or ...-devel packages are missing. The easiest thing to install those is via
$ sudo apt-get build-dep vim-gnome # Debian-based
$ sudo yum-builddep vim-gnome # Redhat
For the Netbeans integration, romainl is probably right in his remark that that is only available in GVIM (but that should be built with your invocation, too).
How can I diagnose this problem?
The way to do it is to manually look back through the ./configure output, and see what things it couldn't find. To do this, and because the output isn't really "user friendly", you got to scroll back and scan the output for lines that end with "no", like:
checking if X11 header files can be found... no
^ that would signal to you you need to install some sort of X11 devel package etc.
Probably you need GUI support to enable netbeans perhaps? I see the "without GUI" part in the Huge version without GUI part.
Doing that manually requires some effort and trial/error intitially. Because to actually get it to compile in GUI support, you have to install a bunch of different packages to get all the right development header files (at least from my personal experience!). So like people have said, try searching for and installing X11 devel packages, and a gtk2-devel package ^^
(I think at one point I got frustrated