OpenDBX/Setup/Common problems - Revision history

213.39.230.78: /* Warning running tests in PostgreSQL */

2009-09-29T20:10:45Z

‎Warning running tests in PostgreSQL

200.69.219.201: Added "Warning running tests in PostgreSQL"

2009-09-29T19:08:59Z

Added "Warning running tests in PostgreSQL"

Nose: readline.h not found

2009-05-16T10:03:38Z

readline.h not found

194.158.241.118: /* C compiler cannot create executables */

2009-02-15T20:27:13Z

‎C compiler cannot create executables

194.158.241.118: /* C compiler cannot create executables */

2009-02-15T20:24:44Z

‎C compiler cannot create executables

Nose: header not found

2008-12-20T12:45:38Z

header not found

Nose: cannot create executables

2008-12-20T10:51:34Z

cannot create executables

New page

__TOC__

== C compiler cannot create executables ==

checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.

And if you see config.log you see:

crt1.o: No such file: No such file or directory

You probably doesn't have installed build-essential package. To fix this you must:

apt-get update
apt-get install build-essential

@@ Line 38: / Line 38: @@
-== Warning running tests in PostgreSQL ==
+== Backslashes in PostgreSQL ==
-Depending on your PostgreSQL configuration you may have the following WARNING when running OpenDBX tests:
+Depending on your PostgreSQL configuration you may have the following warnings when running the OpenDBX tests:
   WARNING:  nonstandard use of \\ in a string literal
   LINE 1: SELECT * FROM odbxtest WHERE col = 'a''''\\''b'
-−
+                                                ^
   HINT:  Use the escape string syntax for backslashes, e.g., E'\\'.
-The problem seems to be an option in the postgresql.conf. See
+The problem is a non-standard option in the postgresql.conf which can be changed by setting
-http://dbaspot.com/forums/postgresql/251026-many-warning-pg-logs-nonstandard-use-string-literalat-character.html for details.
-The solution is to set
   standard_conforming_strings = on
-in postgresql.conf
+in postgresql.conf. For more details you can have a look at a forum comment on

← Older revision		Revision as of 19:08, 29 September 2009
Line 36:		Line 36:

	The readline header and library is required when building the default OpenDBX package but not for the core library itself. If you don't need the odbx-sql utility (the command line tool for executing statements interactively or as batch), you can disable compilation of this part and therefore don't need the readline files too. In this case, please have a look at [[OpenDBX/Setup/Manual_builds#Without_utilities\|manual builds]] section.		The readline header and library is required when building the default OpenDBX package but not for the core library itself. If you don't need the odbx-sql utility (the command line tool for executing statements interactively or as batch), you can disable compilation of this part and therefore don't need the readline files too. In this case, please have a look at [[OpenDBX/Setup/Manual_builds#Without_utilities\|manual builds]] section.
		+
		+
		+	== Warning running tests in PostgreSQL ==
		+
		+	Depending on your PostgreSQL configuration you may have the following WARNING when running OpenDBX tests:
		+
		+	WARNING: nonstandard use of \\ in a string literal
		+	LINE 1: SELECT * FROM odbxtest WHERE col = 'a''''\\''b'
		+	^
		+	HINT: Use the escape string syntax for backslashes, e.g., E'\\'.
		+
		+	The problem seems to be an option in the postgresql.conf. See
		+	http://dbaspot.com/forums/postgresql/251026-many-warning-pg-logs-nonstandard-use-string-literalat-character.html for details.
		+	The solution is to set
		+
		+	standard_conforming_strings = on
		+
		+	in postgresql.conf

← Older revision		Revision as of 10:03, 16 May 2009
Line 32:		Line 32:

	For the major distributions, there's a [[OpenDBX/Setup/Manual_builds#Distribution_specific\|list of non-standard directories]] available.		For the major distributions, there's a [[OpenDBX/Setup/Manual_builds#Distribution_specific\|list of non-standard directories]] available.
		+
		+	== readline.h not found ==
		+
		+	The readline header and library is required when building the default OpenDBX package but not for the core library itself. If you don't need the odbx-sql utility (the command line tool for executing statements interactively or as batch), you can disable compilation of this part and therefore don't need the readline files too. In this case, please have a look at [[OpenDBX/Setup/Manual_builds#Without_utilities\|manual builds]] section.

← Older revision		Revision as of 12:45, 20 December 2008
Line 16:		Line 16:
	apt-get update		apt-get update
	apt-get install build-essential		apt-get install build-essential
		+
		+	== Header not found ==
		+
		+	./configure will search in your computer if you have all the necessary things for compilation. If somethins is missing, you will get an error message like this:
		+
		+	configure: error: <header-file> header not found
		+
		+	This is because it didn't find the header file ( .h ) of an necessary library. In all major Linux/Unix distributions, the header files for libraries are in the development package of that library and its name contains either "-dev" or "-devel". After installing the package, the header file should be available in the standard include path (/usr/include/). If it doesn't (e.g. the MySQL or PostgreSQL header are located in other directories in many distributions), you have to add the location to the CPPFLAGS environment variable like this:
		+
		+	CPPFLAGS="-I/usr/include/mysql" ./configure --with-backends="mysql"
		+
		+	For the major distributions, there's a [[OpenDBX/Setup/Manual_builds#Distribution_specific\|list of non-standard directories]] available.

@@ Line 12: / Line 12: @@
   crt1.o: No such file: No such file or directory
-You probably doesn't have installed build-essential package. To fix this you must:
+You probably don't have the build-essential package installed. To fix this you must:
   apt-get update

@@ Line 16: / Line 16: @@
   apt-get update
   apt-get install build-essential
 == Header not found ==