Closed tschoonj closed 6 years ago
Hm, indien met PKG_CONFIG=/usr/bin/pkg-config
runt het inderdaad de configure
maar nu krijg ik een probleem dat make check
faalt door:
Traceback (most recent call last): File "../../tests/python.py", line 2, in <module> import polycap ImportError: /home/ptack/poly_raytrace/build/src/.libs/libpolycap.so.0: undefined symbol: GOMP_parallel FAIL: python.sh 1 of 7 tests failed
Hey Pieter,
Heb het probleem opgelost door nieuwe versie van autotools te installeren in anaconda.
Doe autoreconf -fi ..
en doe daarna make clean
, ../configure plus opties
, make
, make check
Oke, thanks! Dit blijkt te werken.
Hij geeft precies wel enkele vreemde opmerkingen over configure.ac
bij make
:
configure.ac:25: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
en ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
e.d.
Bij make check
runt hij alles, en hij passed 6 tests. Vreemde is dat ik dacht dat met de python tests er 7 waren, dus die slaat hij over of ...?
Hij zal alleen maar de python test draaien als de optionele python bindings ook effectief gecompileerd geweest zijn.
Kijk eens naar de output van configure: is er ergens een probleem in het stuk waar hij de beschikbaarheid van python en cython nagaat?
Hm, kvind precies nergens vermelding van python of cython :s
[ptack@lvserver:~/poly_raytrace/build] divergence_def(+46/-41)+* � ../configure PKG_CONFIG=/usr/bin/pkg-config CFLAGS="-g -O0" checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define EXTENSIONS... yes checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/local/gcc/7.3.0/bin/ld checking if the linker (/usr/local/gcc/7.3.0/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/local/gcc/7.3.0/bin/nm -B checking the name lister (/usr/local/gcc/7.3.0/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1966080 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/local/gcc/7.3.0/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/local/gcc/7.3.0/bin/nm -B output from gcc object... ok checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/local/gcc/7.3.0/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking whether gcc and cc understand -c and -o together... yes checking for vasprintf... yes checking for strdup... yes checking pkg-config is at least version 0.9.0... yes checking for xraylib... yes checking for gsl... yes checking for easyRNG... no checking for gcc option to support OpenMP... -fopenmp checking for h5cc-64... /usr/bin/h5cc-64 checking for gbasename... no checking for basename... basename checking for gdirname... no checking for dirname... dirname configure: creating ./config.status config.status: creating Makefile config.status: creating include/Makefile config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating example/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands
Ok, ik zie wat er gebeurd is: uw branch is gemaakt voordat ik mijn python branch heb gemerged.
Doe het volgende:
# save al uw bestanden en exit vi
git stash
git fetch origin
git rebase origin/master # normaal gezien zouden er hier geen problemen mogen zijn, indien zo stop en toon mij de error messages
git stash pop
# doe verder uw werk en commit wanneer nodig
git push -f
Should fix the syntax errors seen when running configure generated with CentOS 6' autotools.