Am 21. Dezember 2017 17:37:14 MEZ schrieb Marius Schamschula <address@hidden>:
Hi all,Hi Marius,it has nothing to do with Makefile.in. This seems to be a problematic mkoctfile parameter that comes from Octave in this line:https://sourceforge.net/p/octave/interval/ci/15d1a3142e16a25744a5dcfd3f750d8a53358cbd/tree/src/Makefile#l38I am also not sure how to fix this.Oliver
I just tried updating the interval package to version 3.1.0. However, I
got a build error while building crlibm:
-D_THREAD_SAFE -pthread -pipe -Os -std=c++11 -stdlib=libc++ -arch
x86_64 -bundle -bundle_loader /opt/local/bin/octave-4.2.1 -o
crlibm_function.oct crlibm_function.o crlibm/asincos.o
crlibm/atan_accurate.o crlibm/atan_fast.o crlibm/crlibm_private.o
crlibm/csh_fast.o crlibm/exp-td-standalone.o crlibm/exp-td.o
crlibm/expm1-standalone.o crlibm/expm1.o crlibm/log.o crlibm/log1p.o
crlibm/pow.o crlibm/rem_pio2_accurate.o crlibm/trigo_accurate.o
crlibm/trigo_fast.o crlibm/trigpi.o crlibm/triple-double.o
-L/opt/local/lib -loctinterp -loctave
g++-mp-7: error: unrecognized command line option '-stdlib=libc++'
make: *** [crlibm_function.oct] Error 1
The above option applies to llvm, not gcc. I’m not sure how to tweak
the Makefile.in to fix this.
I’m building against octave 4.2.1, built using gcc 7 under macOS High
Sierra (10.13.3 Beta), under MacPorts.
Thanks for that clarification.
I’ve poked around and had mkoctfile print out the various variables, but could not find anything that would add "-std=c++11 -stdlib=libc++”. Indeed, running ‘strings /opt/local/bin/mkoctfile | grep stdlib’ came up empty.
Thus, this must come in from somewhere else.