Styjun

Resolving moral conflict

Wrong result by FindRoot

What benefits does the Power Word Kill spell have?

Leaving a job that I just took based on false promise of a raise. What do I tell future interviewers?

My 15 year old son is gay. How do I express my feelings about this?

Why is the missed-approach course for the "RNAV (GNSS) - A" approach to runway 28 at ENSB shaped all funny?

What happens if nobody can form a government in Israel?

What is this utensil for?

Does the Orange League not count as an official Pokemon League, making the Alolan League his first-ever win?

How use custom order in folder on Windows 7 and 10

Idiom for "I came, I saw, I ate" (or drank)

What is the lowest voltage that a microcontroller can successfully read on the analog pin?

Social leper versus social leopard

How is the problem, ⟨G⟩ in Logspace?

How to deal with my team leader who keeps calling me about project updates even though I am on leave for personal reasons?

If an object moving in a circle experiences centripetal force, then doesn't it also experience centrifugal force, because of Newton's third law?

reverse a list of generic type

Can this word order be rearranged?

How do I improve in sight reading?

The quicker I go up, the sooner I’ll go down - Riddle

Hilbert's hotel, why can't I repeat it infinitely many times?

Why is there not a feasible solution for a MIP?

What do you do if you have developments on your paper during the long peer review process?

Is there any reason nowadays to use a neon indicator lamp instead of an LED?

Linking to statically compiled z3 needs additional libraries on Linux

When to use dynamic vs. static librariesWhat do 'statically linked' and 'dynamically linked' mean?Do I need static libraries to statically link?Static linking vs dynamic linkingLinux static linking is dead?How can I statically link a C++ library to a C application in OSX?lib OSMesa off-screen context creation fails in C++, but only when statically linkedStatic link libraries in Qt application with CMakeHow to figure out where linking to static library of Boost's thread component is postulated when building Field3D?Compiling and linking static library with gfortran

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

1

I used CMake to compile a static version of (a fairly recent of) z3 using:

cmake -DBUILD_LIBZ3_SHARED=false -DCMAKE_INSTALL_PREFIX=/opt/z3-devel -G "Unix Makefiles" ../

Now when I statically link the library against a C++ program, say this small variation of a z3 example:

#include"z3++.h"
using namespace z3;

int main(int argc, char** argv) 
 config conf;
 context c(conf);
 expr x = c.int_const("x");
 expr y = c.int_const("y");
 expr z = c.int_const("z");
 goal g(c);
 g.add( ((2*x)+y)+z == 4);
 g.add( (x+(2*y))+z == 4);
 g.add( x+y == 4);
 std::cout << g << "n";
 tactic t(c, "fm");
 apply_result r = t(g);
 std::cout << r << "n";
 return 0;

via

g++ -c -I /opt/z3-devel/include -static -o main.o main.cc
g++ -static -L /opt/z3-devel/lib64 -o main main.o -lz3

I receive a long list of undefined reference linking errors. What solves the issue is to add -lgomp -pthread -lrt -ldl as additional libraries. The linker outputs the following warning:

/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/8/libgomp.a(target.o): in function `gomp_target_init':
(.text+0x32c): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Nevertheless, the program runs fine on my own machine and on Starexec.

Is this combination of static and dynamic linking the best I can do? Shouldn't those libraries be already statically linked into libz3.a? I have static versions of gomp, pthread and rt available on the system.

z3 static-linking

share|improve this question

edited Mar 28 at 16:06

lambda.xy.x

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  One immediate thought: I remember that at least on Windows, OpenMP is not available in static form, so the build scripts may be set up to use the dynamic libraries regardless of the target. Going by the warning message from the linker, it looks to be similar on your platform though.
  
  – Christoph Wintersteiger
  Mar 28 at 17:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's well possible - if I understand the cmake flag correctly, this just expresses a preference of static libraries over dynamic ones.It might make sense to raise an issue at the github repository then -- I just want to make sure that this is not a specific problem that only occurs for me.
  
  – lambda.xy.x
  Mar 28 at 17:56
  

  
  
  
  

add a comment
 | 

1

I used CMake to compile a static version of (a fairly recent of) z3 using:

cmake -DBUILD_LIBZ3_SHARED=false -DCMAKE_INSTALL_PREFIX=/opt/z3-devel -G "Unix Makefiles" ../

Now when I statically link the library against a C++ program, say this small variation of a z3 example:

#include"z3++.h"
using namespace z3;

int main(int argc, char** argv) 
 config conf;
 context c(conf);
 expr x = c.int_const("x");
 expr y = c.int_const("y");
 expr z = c.int_const("z");
 goal g(c);
 g.add( ((2*x)+y)+z == 4);
 g.add( (x+(2*y))+z == 4);
 g.add( x+y == 4);
 std::cout << g << "n";
 tactic t(c, "fm");
 apply_result r = t(g);
 std::cout << r << "n";
 return 0;

via

g++ -c -I /opt/z3-devel/include -static -o main.o main.cc
g++ -static -L /opt/z3-devel/lib64 -o main main.o -lz3

I receive a long list of undefined reference linking errors. What solves the issue is to add -lgomp -pthread -lrt -ldl as additional libraries. The linker outputs the following warning:

/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/8/libgomp.a(target.o): in function `gomp_target_init':
(.text+0x32c): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Nevertheless, the program runs fine on my own machine and on Starexec.

Is this combination of static and dynamic linking the best I can do? Shouldn't those libraries be already statically linked into libz3.a? I have static versions of gomp, pthread and rt available on the system.

z3 static-linking

share|improve this question

edited Mar 28 at 16:06

lambda.xy.x

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  One immediate thought: I remember that at least on Windows, OpenMP is not available in static form, so the build scripts may be set up to use the dynamic libraries regardless of the target. Going by the warning message from the linker, it looks to be similar on your platform though.
  
  – Christoph Wintersteiger
  Mar 28 at 17:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's well possible - if I understand the cmake flag correctly, this just expresses a preference of static libraries over dynamic ones.It might make sense to raise an issue at the github repository then -- I just want to make sure that this is not a specific problem that only occurs for me.
  
  – lambda.xy.x
  Mar 28 at 17:56
  

  
  
  
  

add a comment
 | 

I used CMake to compile a static version of (a fairly recent of) z3 using:

cmake -DBUILD_LIBZ3_SHARED=false -DCMAKE_INSTALL_PREFIX=/opt/z3-devel -G "Unix Makefiles" ../

Now when I statically link the library against a C++ program, say this small variation of a z3 example:

#include"z3++.h"
using namespace z3;

int main(int argc, char** argv) 
 config conf;
 context c(conf);
 expr x = c.int_const("x");
 expr y = c.int_const("y");
 expr z = c.int_const("z");
 goal g(c);
 g.add( ((2*x)+y)+z == 4);
 g.add( (x+(2*y))+z == 4);
 g.add( x+y == 4);
 std::cout << g << "n";
 tactic t(c, "fm");
 apply_result r = t(g);
 std::cout << r << "n";
 return 0;

via

g++ -c -I /opt/z3-devel/include -static -o main.o main.cc
g++ -static -L /opt/z3-devel/lib64 -o main main.o -lz3

I receive a long list of undefined reference linking errors. What solves the issue is to add -lgomp -pthread -lrt -ldl as additional libraries. The linker outputs the following warning:

/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/8/libgomp.a(target.o): in function `gomp_target_init':
(.text+0x32c): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Nevertheless, the program runs fine on my own machine and on Starexec.

Is this combination of static and dynamic linking the best I can do? Shouldn't those libraries be already statically linked into libz3.a? I have static versions of gomp, pthread and rt available on the system.

z3 static-linking

share|improve this question

edited Mar 28 at 16:06

lambda.xy.x

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges

cmake -DBUILD_LIBZ3_SHARED=false -DCMAKE_INSTALL_PREFIX=/opt/z3-devel -G "Unix Makefiles" ../

#include"z3++.h"
using namespace z3;

int main(int argc, char** argv) 
 config conf;
 context c(conf);
 expr x = c.int_const("x");
 expr y = c.int_const("y");
 expr z = c.int_const("z");
 goal g(c);
 g.add( ((2*x)+y)+z == 4);
 g.add( (x+(2*y))+z == 4);
 g.add( x+y == 4);
 std::cout << g << "n";
 tactic t(c, "fm");
 apply_result r = t(g);
 std::cout << r << "n";
 return 0;

g++ -c -I /opt/z3-devel/include -static -o main.o main.cc
g++ -static -L /opt/z3-devel/lib64 -o main main.o -lz3

/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/8/libgomp.a(target.o): in function `gomp_target_init':
(.text+0x32c): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

share|improve this question

edited Mar 28 at 16:06

lambda.xy.x

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges

share|improve this question

edited Mar 28 at 16:06

lambda.xy.x

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges

asked Mar 28 at 15:58

lambda.xy.xlambda.xy.x

3,4741616 silver badges2828 bronze badges