Bug 252

Summary: Meet a strange problem when compiling vim7.3 if set --build=iX86-linux
Product: [Build System, Metadata & Runtime] OE-Core Reporter: liping Ke <liping.ke>
Component: devtools / tool chainAssignee: Joshua Lock - Disabled <josh>
Status: VERIFIED NOTABUG QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, kevin.tian, lianhao.lu, liping.ke, meta.mr.watcher, meta.watcher, sgw
Version: 0.9   
Target Milestone: 0.9 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description liping Ke 2010-08-31 20:19:26 UTC
Hi, Josh

If I set --build=XXXX, I will meet configure error when compiling vim73:

Reproduce steps:
1) http://www.vim.org/sources.php, get vim-7.3.tar.bz2 and exract it
2) source /opt/poky/environment-setupXXX
3) cd vim73
4) ./configure --target=i586-poky-linux --host=i586-poky-linux --build=i586-linux


Error then happens.

If I remove --build=i586-linux, only running $./configure --target=i586-poky-linux --host=i586-poky-linux everything is fine. I am not sure whether this is a problem or not since vim is not a complete autotool project, it only contains executable ./configure.

Thanks& Regards,
criping






Paste error below:
configure: loading cache auto/config.cache checking whether make sets $(MAKE)... yes checking for i586-poky-linux-gcc... i586-poky-linux-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... 
checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i586-poky-linux-gcc accepts -g... yes checking for i586-poky-linux-gcc option to accept ISO C89... none needed checking how to run the C preprocessor... i586-poky-linux-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for library containing strerror... none required checking for gawk... gawk checking for strip... strip checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes cannot compile a simple program; if not cross compiling check CC and CFLAGS
configure: checking for buggy tools...
- sh is	'GNU bash, version 4.1.5(1)-release (i486-pc-linux-gnu)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.' - probably OK.
- sed is	'GNU sed version 4.2.1
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE, to the extent permitted by law.

GNU sed home page: <http://www.gnu.org/software/sed/>.
General help using GNU software: <http://www.gnu.org/gethelp/>.
E-mail bug reports to: <bug-gnu-utils@gnu.org>.
Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.'.
checking for BeOS... no
checking for QNX... no
checking for Darwin (Mac OS X)... no
checking --with-vim-name argument... Defaulting to vim checking --with-ex-name argument... Defaulting to ex checking --with-view-name argument... Defaulting to view checking --with-global-runtime argument... no checking --with-modified-by argument... no checking if character set is EBCDIC... no checking --disable-selinux argument... no checking for is_selinux_enabled in -lselinux... no checking --with-features argument... Defaulting to normal checking --with-compiledby argument... no checking --disable-xsmp argument... no checking --disable-xsmp-interact argument... no checking --enable-luainterp argument... no checking --enable-mzschemeinterp argument... no checking --enable-perlinterp argument... no checking --enable-pythoninterp argument... no checking --enable-python3interp argument... no checking --enable-tclinterp argument... no checking --enable-rubyinterp argument... no checking --enable-cscope argument... no checking --enable-workshop argument... no checking --disable-netbeans argument... no checking for socket in -lsocket... no checking for gethostbyname in -lnsl... yes checking whether compiling netbeans integration is possible... yes checking --enable-sniff argument... no checking --enable-multibyte argument... no checking --enable-hangulinput argument... no checking --enable-xim argument... defaulting to auto checking --enable-fontset argument... no checking for xmkmf... no checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking if X11 header files can be found... yes checking for _XdmcpAuthDoIt in -lXdmcp... no checking for IceOpenConnection in -lICE... no checking for XpmCreatePixmapFromData in -lXpm... no checking if X11 header files implicitly declare return values... no checking size of wchar_t is 2 bytes... configure: error: failed to compile test program
Comment 1 Joshua Lock - Disabled 2010-09-02 10:48:31 UTC
I've not yet had time to look at this but can you clarify if this bug is against the meta-toolchain or an SDK image.
Comment 2 Joshua Lock - Disabled 2010-09-09 06:55:30 UTC
This is almost definitely a problem with Vim. The build system in Vim is not very cross-compile friendly.

I can coerce Vim 7.2 into configuring with:

./configure --build=i586-linux --host=i586-poky-linux --target=i586-poky-linux --enable-gui=none --disable-gtktest --disable-xim --with-features=big --disable-gpm --without-x --disable-netbeans vim_cv_toupper_broken=no vim_cv_terminfo=yes vim_cv_tty_group=world vim_cv_getcwd_broken=no vim_cv_stat_ignores_slash=no ac_cv_small_wchar_t="no" ac_cv_sizeof_int=4 vim_cv_memmove_handles_overlap=yes --with-tlib=ncurses

But some new changes to Vim 7.3's make system mean it's more difficult. The easiest thing to do is to apply a patch like the on Gentoo developed turning the uint32_t error into a warning: http://bugs.gentoo.org/attachment.cgi?id=243615

Resolving as NOTABUG because this is not a bug in Poky.
Comment 3 liping Ke 2010-09-13 02:14:27 UTC
Thanks for the detailed info.
This bug could be closed.