Support #1700
boost_1_80_0
Description
Problems and solutions
Related issues
History
#1 Updated by Anna Maria Bigatti over 1 year ago
- % Done changed from 0 to 80
- Estimated time set to 2.00 h
Problems with
make[2]: *** No rule to make target `../../configuration/ExternalLibs/include/boost/system/detail/to_std_category.hpp', needed by `AST.o'. Stop.
?
just run make veryclean
to remake dependencies: there is no to_std_category.hpp
in boost_1_80_0
#2 Updated by Anna Maria Bigatti over 1 year ago
- Related to Design #1697: Specifying BOOST in configure added
#3 Updated by Anna Maria Bigatti over 1 year ago
- Related to Design #1696: Which BOOST libs are actually needed? added
#4 Updated by Anna Maria Bigatti over 1 year ago
- Related to Bug #1695: boost-find-lib.sh added
#5 Updated by John Abbott over 1 year ago
- Status changed from New to Resolved
I wonder if there is a simple away to warn users of potential problems?
A similar problem could arise with any of the external libs, and the
solution is no doubt to rebuild dependencies -- and this should normally
be done by re-running configure
(which may include some other "sanity
checks" for external libs).
Here is an idea:
for each ext lib configure
computes a check-sum for some header file
in that ext lib, and saves the result in autoconf.mk
. Then make
can verify that the check-sums are correct -- if not, a warning with
a delay, can be produced before proceeding with compilation.
[the delay gives the user a chance to hit Ctrl-C]
#6 Updated by Anna Maria Bigatti over 1 year ago
I still have some warnings, but it compiles and works fine
bash-3.2$ g++ -std=c++14 -Wall -pedantic -O2 -I../../include -I ../../configuration/ExternalLibs/include -g -DCoCoA_WITH_READLINE AST.o Lexer.o Main.o Interpreter.o LineProviders.o Parser.o CoCoALibSupplement.o BuiltInFunctions.o BuiltInFunctions-CoCoALib.o BuiltInFunctionsVarArgs-CoCoALib.o BuiltInOneLiners-CoCoALib.o BuiltInFunctions-Frobby.o BuiltInFunctions-GFan.o BuiltInFunctions-GSL.o BuiltInFunctions-MathSAT.o BuiltInFunctions-Normaliz.o globals.o OnlineHelp.o VersionInfo.o Banner.o CompilationDate.o -o CoCoAInterpreter ../../lib/libcocoa.a -L../../configuration/ExternalLibs/lib -lfrobby-symlink -lgfan-symlink -lcddgmp-symlink -lmathsat-symlink -lnormaliz-symlink -lgmpxx-symlink -lgmp-symlink /Users/bigatti/0.99/boost_1_80_0/lib/libboost_filesystem.a /Users/bigatti/0.99/readline-7.0/lib/libreadline.a -ltermcap -lpthread ld: warning: PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not allowed in code signed PIE, but used in ___gmpn_divexact_1 from ../../configuration/ExternalLibs/lib/libgmp-symlink.a(dive_1.o). To fix this warning, don't compile with -mdynamic-no-pic or link with -Wl,-no_pie ld: warning: direct access in function 'boost::system::error_code::what() const' from file '/Users/bigatti/0.99/boost_1_80_0/lib/libboost_filesystem.a(exception.o)' to global weak symbol 'boost::system::error_code::location() const::loc' from file 'AST.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings. ld: warning: direct access in function 'boost::system::error_code::what() const' from file '/Users/bigatti/0.99/boost_1_80_0/lib/libboost_filesystem.a(exception.o)' to global weak symbol 'boost::system::error_code::location() const::loc' from file 'AST.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings. ld: warning: direct access in function 'boost::system::error_code::what() const' from file '/Users/bigatti/0.99/boost_1_80_0/lib/libboost_filesystem.a(exception.o)' to global weak symbol 'boost::system::error_code::location() const::loc' from file 'AST.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
#7 Updated by Anna Maria Bigatti over 1 year ago
- Related to Design #1528: MacOS compilation with clang added
#8 Updated by Anna Maria Bigatti over 1 year ago
- Related to Support #632: MacOSX: many warnings with compiler CLANG/LLVM when compiling BOOST code. added
#9 Updated by John Abbott over 1 year ago
On my MacBook I get over 100000 (one hundred thousand) lines of warnings when compiling.
I think there is some mild incompatibility between BOOST and the compiler (g++
on MacOS)
My proposal in note 5 is not unreasonable, but is it really KISS?
#10 Updated by John Abbott over 1 year ago
- Related to Bug #1600: Detect updated versions of external libs added
#11 Updated by John Abbott over 1 year ago
- Status changed from Resolved to Closed
- Assignee set to John Abbott
- % Done changed from 80 to 100
- Estimated time changed from 2.00 h to 3.99 h