[Octave-bug-tracker] [bug #41024] 3.8.0 build fails with syntax error near unexpected token `('

[Rik]

Update of bug #41024 (project octave):

                  Status:                    None => In Progress            

    _______________________________________________________

Follow-up Comment #2:

What about modifying configure.ac to wrap the -I option in double quotes for
Windows systems?  At line 2555 of configure.ac there is a case statement which
checks for MinGW or Cygwin and sets the JAVA variables appropriately.


mingw* | cygwin*)
  build_java=yes
  JAVA_LIBS=-ladvapi32
  if test $have_msvc = no; then
    if test -n "$JAVA_CPPFLAGS"; then
      JAVA_CPPFLAGS="-I${JAVA_CPPFLAGS}/include
-I${JAVA_CPPFLAGS}/include/win32"
    else
      JAVA_CPPFLAGS="-I${JAVA_HOME}/include -I${JAVA_HOME}/include/win32"
    fi
    LDFLAGS="$LDFLAGS -Wl,--export-all-symbols"
  fi
  AC_DEFINE(HAVE_JAVA, 1,
    [Define to 1 if Java is available and is at least version 1.5])
  break


I think we could change the JAVA_CPPFLAGS lines to enclose the JAVA_HOME or
JAVA_CPPFLAGS in quotes.  See the sample below.


JAVA_CPPFLAGS="-I\"${JAVA_HOME}\"/include -I\"${JAVA_HOME}\"/include/win32"


The original poster can test this by modifying the configure script to add the
escaped double quotes as shown above and then re-running the ./configure; make
cycle.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41024>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/