thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity

patch 8.0.1710: building with Ruby fails

Browse Source 
Problem:    Building with Ruby fails.
Solution:   Don't add -ansi when building with Ruby.
This commit is contained in:
Bram Moolenaar
2018-04-14 16:12:30 +02:00
parent 2e324950b8
commit 2a43230ce3
3 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/auto/configure vendored
View File

@@ -14434,7 +14434,7 @@ if test "$zOSUnix" = "yes"; then
CFLAGS="-D_ALL_SOURCE -Wc,float\(ieee\),dll" CFLAGS="-D_ALL_SOURCE -Wc,float\(ieee\),dll"
fi 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" CFLAGS="$CFLAGS -ansi"
fi fi

7
src/configure.ac
View File

@@ -4403,9 +4403,10 @@ if test "$zOSUnix" = "yes"; then
CFLAGS="-D_ALL_SOURCE -Wc,float\(ieee\),dll" CFLAGS="-D_ALL_SOURCE -Wc,float\(ieee\),dll"
fi fi
dnl Declare what standards the code should comply with. But not when using dnl Declare what standards the code should comply with.
dnl GTK, the header files cause all kinds of warnings. dnl But not when using GTK, the header files cause all kinds of warnings.
if test "$GCC" = yes -a "$GUITYPE" != "GTK"; then 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" CFLAGS="$CFLAGS -ansi"
fi fi

2
src/version.c
View File

@@ -762,6 +762,8 @@ static char *(features[]) =
static int included_patches[] = static int included_patches[] =
{ /* Add new patch number below this line */ { /* Add new patch number below this line */
/**/
1710,
/**/ /**/
1709, 1709,
/**/ /**/