Mercurial > vim
changeset 13676:6b49b6ea9e43 v8.0.1710
patch 8.0.1710: building with Ruby fails
commit https://github.com/vim/vim/commit/2a43230ce39eea340aab15fb50a083bc527fb8d0
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Apr 14 16:12:30 2018 +0200
patch 8.0.1710: building with Ruby fails
Problem: Building with Ruby fails.
Solution: Don't add -ansi when building with Ruby.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sat, 14 Apr 2018 16:15:06 +0200 |
parents | c0d899844b06 |
children | 4efb4683ea71 |
files | src/auto/configure src/configure.ac src/version.c |
diffstat | 3 files changed, 7 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/src/auto/configure +++ b/src/auto/configure @@ -14434,7 +14434,7 @@ if test "$zOSUnix" = "yes"; then CFLAGS="-D_ALL_SOURCE -Wc,float\(ieee\),dll" fi -if test "$GCC" = yes -a "$GUITYPE" != "GTK"; then +if test "$GCC" = yes -a "$GUITYPE" != "GTK" -a "X$RUBY_CFLAGS" = "X"; then CFLAGS="$CFLAGS -ansi" fi
--- a/src/configure.ac +++ b/src/configure.ac @@ -4403,9 +4403,10 @@ if test "$zOSUnix" = "yes"; then CFLAGS="-D_ALL_SOURCE -Wc,float\(ieee\),dll" fi -dnl Declare what standards the code should comply with. But not when using -dnl GTK, the header files cause all kinds of warnings. -if test "$GCC" = yes -a "$GUITYPE" != "GTK"; then +dnl Declare what standards the code should comply with. +dnl But not when using GTK, the header files cause all kinds of warnings. +dnl But not when using Ruby, it needs "inline". +if test "$GCC" = yes -a "$GUITYPE" != "GTK" -a "X$RUBY_CFLAGS" = "X"; then CFLAGS="$CFLAGS -ansi" fi