diff options
| author | Hoang M. Le <hle@cs.uni-bremen.de> | 2016-12-21 21:51:26 +0100 |
|---|---|---|
| committer | Dan Liew <delcypher@gmail.com> | 2016-12-28 09:59:21 +0000 |
| commit | ad22e8420fb2f4fa1d98a3753ac844c3dd27d8ce (patch) | |
| tree | 9356a07b47e23be102ca59f13222d8bd42515ba3 /MetaSMT.mk | |
| parent | 3a0f6fdd6815442c504447927fcf204118c62cb7 (diff) | |
| download | klee-ad22e8420fb2f4fa1d98a3753ac844c3dd27d8ce.tar.gz | |
Fix two issues with AC_LINK_IFELSE for metaSMT:
1. It expects only 2 arguments, so if linking succeeds, nothing will happen (thanks to []),
otherwise the message "checking for new_bitvector() in -lmetaSMT" will appear.
The latter is that what we currently observe, which means linking actually failed.
2. The reason for linking failure is the use of "-lmetaSMT" in LDFLAGS.
AC_LINK_IFELSE does approximately the following: ${CXX} ... -lmetaSMT ${EXECUTABLE_NAME} ${LIBS},
which causes "libmetaSMT cannot be found" (at least on Ubuntu Xenial, where ${LIBS} = -lz).
After consulting https://www.gnu.org/software/autoconf/manual/autoconf-2.66/html_node/Running-the-Linker.html,
adding "-lmetaSMT" to ${LIBS} seems to be the correct solution.
Diffstat (limited to 'MetaSMT.mk')
0 files changed, 0 insertions, 0 deletions