8 files changed, 8 insertions, 14 deletions
diff --git a/lib/odbc/c_src/Makefile.in b/lib/odbc/c_src/Makefile.in
index 784e73c47e..294d832797 100644
--- a/lib/odbc/c_src/Makefile.in
+++ b/lib/odbc/c_src/Makefile.in
@@ -52,7 +52,7 @@ RELSYSDIR = $(RELEASE_PATH)/lib/odbc-$(VSN)
 # Target Specs
 # ----------------------------------------------------
 EI_ROOT = $(ERL_TOP)/lib/erl_interface
-EI_INCLUDE = -I$(EI_ROOT)/include
+EI_INCLUDE = -I$(EI_ROOT)/include -I$(EI_ROOT)/include/$(TARGET)
 ifeq ($(findstring win32,$(TARGET)),win32)
 EI_LIB = -lerl_interface_md -lei_md 
 ENTRY_OBJ=$(ERL_TOP)/erts/obj/$(TARGET)/port_entry.o
diff --git a/lib/odbc/configure.in b/lib/odbc/configure.in
index 2dec6e5abf..c5cf2786ca 100644
--- a/lib/odbc/configure.in
+++ b/lib/odbc/configure.in
@@ -21,12 +21,6 @@ dnl
 dnl define([AC_CACHE_LOAD], )dnl
 dnl define([AC_CACHE_SAVE], )dnl
 
-if test "x$no_recursion" != "xyes" -a "x$OVERRIDE_CONFIG_CACHE" = "x"; then
-    # We do not want to use a common cache!
-    cache_file=/dev/null
-fi
-
-
 
 dnl Process this file with autoconf to produce a configure script.
 AC_INIT(c_src/odbcserver.c)
diff --git a/lib/odbc/doc/src/databases.xml b/lib/odbc/doc/src/databases.xml
index a060f87e46..614c327a46 100644
--- a/lib/odbc/doc/src/databases.xml
+++ b/lib/odbc/doc/src/databases.xml
@@ -65,7 +65,7 @@
     <p>Another obstacle is that some drivers do not support scrollable
       cursors which has the effect that the only way to traverse the
       result set is sequentially, with next, from the first row to the
-      last, and once you pass a row you can not go back. This means
+      last, and once you pass a row you cannot go back. This means
       that some functions in the interface will not work together with
       certain drivers. A similar problem is that not all drivers
       support "row count" for select queries, hence resulting in that
diff --git a/lib/odbc/doc/src/error_handling.xml b/lib/odbc/doc/src/error_handling.xml
index 4c80cff12f..8d794d2c99 100644
--- a/lib/odbc/doc/src/error_handling.xml
+++ b/lib/odbc/doc/src/error_handling.xml
@@ -138,7 +138,7 @@
          should be run through the erlang port was not compiled for
          your platform.</item>
         <item>Errors discovered by the ODBC driver - If calls to the
-         ODBC-driver fails due to circumstances that can not be
+         ODBC-driver fails due to circumstances that cannot be
          controlled by the Erlang ODBC application programmer, an
          error string will be dug up from the driver.  This string
          will be the <c>Reason</c> in the <c>{error, Reason} </c>
diff --git a/lib/odbc/doc/src/getting_started.xml b/lib/odbc/doc/src/getting_started.xml
index f2ff8b8993..b27754ff22 100644
--- a/lib/odbc/doc/src/getting_started.xml
+++ b/lib/odbc/doc/src/getting_started.xml
@@ -50,7 +50,7 @@
        and paths to appropriate values. This may differ a lot
        between different os's, databases and ODBC drivers. This
        is a configuration problem related to the third party product
-       and hence we can not give you a standard solution in this guide.</item>
+       and hence we cannot give you a standard solution in this guide.</item>
       <item>The Erlang ODBC application consists of both <c>Erlang</c>
        and <c>C</c> code. The <c>C</c> code is delivered as a
        precompiled executable for windows, solaris and linux (SLES10) in the commercial
diff --git a/lib/odbc/doc/src/notes_history.xml b/lib/odbc/doc/src/notes_history.xml
index 22a92f67cd..d0c0a472e7 100644
--- a/lib/odbc/doc/src/notes_history.xml
+++ b/lib/odbc/doc/src/notes_history.xml
@@ -63,7 +63,7 @@
       <list type="bulleted">
         <item>
           <p>The erlang odbc process will now die normally if a
-            connection can not be established. No connection no
+            connection cannot be established. No connection no
             process it is expected. And as the client has already
             received the error message that would be the reason with
             which the erlang process would be stopped, the supervisor
@@ -193,7 +193,7 @@
         </item>
         <item>
           <p>The erlang odbc process will now die normally if a
-            connection can not be established. No connection no
+            connection cannot be established. No connection no
             process it is expected. And as the client has already
             received the error message that would be the reason with
             which the erlang process would be stopped, the supervisor
diff --git a/lib/odbc/doc/src/odbc.xml b/lib/odbc/doc/src/odbc.xml
index 4d941b3b36..1a3063e6ce 100644
--- a/lib/odbc/doc/src/odbc.xml
+++ b/lib/odbc/doc/src/odbc.xml
@@ -246,7 +246,7 @@
         <p>Closes a connection to a database. This will also
           terminate all processes that may have been spawned 
           when the connection was opened. This call will always succeed.
-          If the connection can not be disconnected gracefully it will
+          If the connection cannot be disconnected gracefully it will
           be brutally killed. However you may receive an error message
           as result if you try to disconnect a connection started by another
           process.
diff --git a/lib/odbc/test/odbc_connect_SUITE.erl b/lib/odbc/test/odbc_connect_SUITE.erl
index 261dfc6f20..94ca62b3fb 100644
--- a/lib/odbc/test/odbc_connect_SUITE.erl
+++ b/lib/odbc/test/odbc_connect_SUITE.erl
@@ -259,7 +259,7 @@ not_exist_db(_Config)  ->
 
 %%-------------------------------------------------------------------------
 no_c_executable() ->
-    [{doc,"Test what happens if the port-program can not be found"}].
+    [{doc,"Test what happens if the port-program cannot be found"}].
 no_c_executable(_Config) ->
     process_flag(trap_exit, true),
     Dir = filename:nativename(filename:join(code:priv_dir(odbc),