Build Problems - Revision history

Taking: /* Profiling */

2012-12-07T01:04:15Z

‎Profiling

2012-12-07T01:03:44Z

‎Profiling

2012-12-07T00:57:13Z

‎google perftools not linking

2012-12-07T00:45:22Z

‎Profiling

2012-12-06T22:44:22Z

‎Custom CLN Library Installations

2012-12-01T02:18:02Z

‎Custom CLN Library Installations

2012-12-01T01:14:23Z

‎Self Compiled CLN

2012-12-01T01:13:32Z

‎libcvc4 without make install

2012-11-30T23:01:52Z

‎make install to a non-standard prefix

2012-11-29T20:07:33Z

‎builds Directory

@@ Line 83: / Line 83: @@
 =Profiling=
 ==SIGPROF handler is already in use==
@@ Line 93: / Line 102: @@
 [http://stackoverflow.com/questions/9577627/ubuntu-11-10-linking-perftools-library]. However, this cannot be applied directly. Something in libtool messes this up.  So the following instead:
   ./configure --with-google-perftools LDFLAGS="-Wl,--no-as-needed /usr/lib/libprofiler.so -Wl,--as-needed" ...

@@ Line 83: / Line 83: @@
 =Profiling=
---enable-profiling and --with-google-perftools are mutually exclusive.  Both require being the handler of SIGPROF on a a number of systems. If you see the following error you are likely doing this.
   Disabling profiler because SIGPROF handler is already in use.
 ==google perftools not linking==

@@ Line 87: / Line 87: @@
 ==google perftools not linking==
-If libprofiler.so.0 is not showing up in ldd CVC4/builds/bin/cvc4 with --with-google-perftools enabled, you may have a problem like the following:
+If libprofiler.so.0 is not showing up in <code>ldd CVC4/builds/bin/cvc4</code> with --with-google-perftools enabled, you may have a problem like the following:
-[http://stackoverflow.com/questions/9577627/ubuntu-11-10-linking-perftools-library]
+[http://stackoverflow.com/questions/9577627/ubuntu-11-10-linking-perftools-library]. However, this cannot be applied directly. Something in libtool messes this up.  So the following instead:
 ==Google Perftools And Early Exit==

@@ Line 85: / Line 85: @@
 --enable-profiling and --with-google-perftools are mutually exclusive.  Both require being the handler of SIGPROF on a a number of systems. If you see the following error you are likely doing this.
   Disabling profiler because SIGPROF handler is already in use.
 ==Google Perftools And Early Exit==

← Older revision		Revision as of 22:44, 6 December 2012
Line 81:		Line 81:
	Putting this all together:		Putting this all together:
	LD_LIBRARY_PATH="$CLN/lib/" ./configure --with-cln CLN_CFLAGS="-I$CLN/include/cln/" CLN_LIBS="-L$CLN/lib/" CPPFLAGS="-I$CLN/include/" LDFLAGS="-L$CLN/lib/" LIBS="-lcln" ...		LD_LIBRARY_PATH="$CLN/lib/" ./configure --with-cln CLN_CFLAGS="-I$CLN/include/cln/" CLN_LIBS="-L$CLN/lib/" CPPFLAGS="-I$CLN/include/" LDFLAGS="-L$CLN/lib/" LIBS="-lcln" ...
		+
		+	=Profiling=
		+	--enable-profiling and --with-google-perftools are mutually exclusive. Both require being the handler of SIGPROF on a a number of systems. If you see the following error you are likely doing this.
		+	Disabling profiler because SIGPROF handler is already in use.
		+
		+	==Google Perftools And Early Exit==
		+	Are you getting empty files or no output from google perftools? Make sure to disable early exiting with "--no-early-exit".
		+	$ CPUPROFILE=example.prof ./cvc4 --no-early-exit example.smt
		+	unsat
		+	PROFILE: interrupts/evictions/bytes = 9/0/1512
		+	$ ls -l example.prof
		+	-rw-r--r-- 1 taking taking 8784 Dec 6 17:39 example.prof
		+	If you try to do this without "--no-early-exit", example.prof is empty.

@@ Line 73: / Line 73: @@
 Suppose you have CLN make installed to a custom target. I'll assume the full path is in $CLN.  (I have only done this once so it might not be minimal.) You are going to have to play with ALL of the following flags when configuring:
 * --with-cln
-* CLN_CFLAGS="-I$CLN/include/cln/" (not sure if this is needed)
+* CLN_CFLAGS="-I$CLN/include/cln/"
-* CLN_LIBS="-L$CLN/lib/" (not sure if this is needed)
+* CLN_LIBS="-L$CLN/lib/"
 * LD_LIBRARY_PATH : to get configure's gcc instances to be able to use -lcln
 * CPPFLAGS="-I$CLN/include/"

← Older revision		Revision as of 01:13, 1 December 2012
Line 69:		Line 69:
	$ LD_LIBRARY_PATH="$CVC4/builds/lib/" ./hello		$ LD_LIBRARY_PATH="$CVC4/builds/lib/" ./hello
	We do not endorse with as a permanent solution, but it'll get you up and running fast. For more information, on shared libraries [http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html].		We do not endorse with as a permanent solution, but it'll get you up and running fast. For more information, on shared libraries [http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html].
		+
		+	=Self Compiled CLN=
		+	Suppose you have CLN make installed to a custom target. I'll assume the full path is in $CLN. (I have only done this once so it might not be minimal.) You are going to have to play with ALL of the following flags when configuring:
		+	* --with-cln
		+	* CLN_CFLAGS="-I$CLN/include/cln/" : not sure if this is needed
		+	* CLN_LIBS="-L$CLN/lib/" : not sure if this is needed
		+	* LD_LIBRARY_PATH : to get configure's gcc instances to be able to use -lcln
		+	* CPPFLAGS="-I$CLN/include/"
		+	* LDFLAGS="-L$CLN/lib/"
		+	* LIBS="-lcln"
		+	Putting this all together:
		+	LD_LIBRARY_PATH="$CLN/lib/" ./configure --with-cln CLN_CFLAGS="-I$CLN/include/cln/" CLN_LIBS="-L$CLN/lib/" CPPFLAGS="-I$CLN/include/" LDFLAGS="-L$CLN/lib/" LIBS="-lcln" ...

@@ Line 42: / Line 42: @@
   $ cd $CVC4
   $ mkdir target
-  $ ./configure --prefix=target ...
+  $ ./configure --prefix=`pwd`/target ...
   $ make install
 You can then link against CVC4 by adding the following to the g++ command line:

@@ Line 32: / Line 32: @@
 CVC4 allows for having multiple architectures and configuration options built in the same builds/ directory.  For example, I currently have 3 different significantly different configurations for the <code>x86_64-unknown-linux-gnu</code> architecture.
   $ ls builds/x86_64-unknown-linux-gnu/
-  debug  debug-staticbinary  production-cln-staticbinary To switch in between these, all you need to do is rerun <code>./configure</code>.  This makes it easy to switch between these three configurations.
+  debug  debug-staticbinary  production-cln-staticbinary
 This does make it a bit difficult to find things sometimes. Especially when working on the build system itself, and something goes wrong.